patternMinor
Tool for storing per environment configuration
Viewed 0 times
perenvironmentforconfigurationstoringtool
Problem
I have a requirement to store configuration information on a per environment basis in a tool.
This is a tool with a GUI for adding/updating configuration values (e.g connection strings). This should have a default value and be able to change this based on different environments.
There should be an API to retrieve these configuration values during deployment to a particular environment to add to the application.
I have searched for a while and can't see any tools that would fit this bill. Are there any suggestions?
Note: Currently the settings are in TeamCity variables and deployment is via PowerShell scripts.
This is a tool with a GUI for adding/updating configuration values (e.g connection strings). This should have a default value and be able to change this based on different environments.
There should be an API to retrieve these configuration values during deployment to a particular environment to add to the application.
I have searched for a while and can't see any tools that would fit this bill. Are there any suggestions?
Note: Currently the settings are in TeamCity variables and deployment is via PowerShell scripts.
Solution
There are many tools that can do something like this, including configuration management tools like Chef, Ansible, or Puppet; and KVS tools like Consul and etcd. You could also integrate it as a build step in your CI server, or sidestep the issue using live configuration at runtime against an external configuration store (again, something like Consul or etcd, or any database at all).
Context
StackExchange DevOps Q#690, answer score: 6
Revisions (0)
No revisions yet.