Category: Software, Kubernetes, Infrastructure, encryption, yaml
This post intends to share my experience in defining configuration for software products that require a large number of configurations.
At this point, the user may lose in a sea of configurations if the developer does not correctly place those configurations in proper order and if documentation is completed.
You can use YAML and TOML to define more complex configurations such as hierarchical config structures.
The simplest solution is to create a single object that can be able to hold all configs and replace it with all of the places where configuration reading.
You can use the puppet template to create the template and use the Puppet master to configure the product as you wish.
At this point, the user may lose in a sea of configurations if the developer does not correctly place those configurations in proper order and if documentation is completed.
You can use YAML and TOML to define more complex configurations such as hierarchical config structures.
The simplest solution is to create a single object that can be able to hold all configs and replace it with all of the places where configuration reading.
You can use the puppet template to create the template and use the Puppet master to configure the product as you wish.
Related Articles
Community Partners
DevOps Careers