New ask Hacker News story: Ask HN: How do you manage the high number of configuration properties?
Ask HN: How do you manage the high number of configuration properties?
3 by devops-hs | 1 comments on Hacker News.
We use Terraform to provision most of our infrastructure. The configuration values are stored in TF vars. Our JAVA-based microservices use Spring Cloud Config to manage environment properties, and GO-based microservices use environment var via Viper. Then our mobile apps use Firebase, while our web apps use config files in the repo where either direct files are stored or are somehow interpolated between kustomization YAML templates. Some teams also store configurations in S3. The values for these configurations across all environments are just spread all over the place. A new developer joining the team spends a high amount of time understanding the existing configurations. Triaging live issues has also become problematic. More recently, we added a new cloud, causing a drift in the property values across these clouds. How has your organization solved this problem?
3 by devops-hs | 1 comments on Hacker News.
We use Terraform to provision most of our infrastructure. The configuration values are stored in TF vars. Our JAVA-based microservices use Spring Cloud Config to manage environment properties, and GO-based microservices use environment var via Viper. Then our mobile apps use Firebase, while our web apps use config files in the repo where either direct files are stored or are somehow interpolated between kustomization YAML templates. Some teams also store configurations in S3. The values for these configurations across all environments are just spread all over the place. A new developer joining the team spends a high amount of time understanding the existing configurations. Triaging live issues has also become problematic. More recently, we added a new cloud, causing a drift in the property values across these clouds. How has your organization solved this problem?
Comments
Post a Comment