CODEWITHSUNDEEP
gitversion-controlconfigurationansibledevops
ambe5960
ambe5960

Reputation: 2000

managing sensitive settings and configuration files across servers and development environments

What do medium sized companies use for managing sensitive settings and configuration files across servers and development environment? I work with a small team of developers, and a decent pool of servers. Using a configuration management tool like Ansible seems to have run its course, as it's just not very efficient when releasing code multiple times per day. Far too often are developers waiting for someone to push settings and configuration changes to the servers via Ansible before they can release code. Instead, I would think keeping the files encrypted somewhere and having them loaded as part of the deploy process would be a better option. Is this standard procedure? Any advice or experience would be greatly appreciated!

Upvotes: 0

Views: 76

Answers (1)

flxPeters
flxPeters

Reputation: 1542

You should use Ansible Vault for this. To decrypt, you can share a password, or as i do a password file. So your passwords etc can stay in git, but they are encrypted.

Upvotes: 0

Related Questions