Source: devops.com
The Pros and Cons of Configuration-as-CodeCategory: Kubernetes, Infrastructure
Configuration-as-code, or “GitOps” as many are now calling it, is a simple but astounding idea: Standardize configuration, check it into version control; no need for each Operations/DevOps person to develop their own set of scripts to get the job done. Configuring or reconfiguring an environment is as simple as checkout and run, assuming everything in the configuration is tested.
The volume of change in things such as storage allocation, routing and VLANs is not the volume of change that an agile project sees. Good documentation is as solid a solution as configuration as code for something that changes rarely and the size/number of scripts and configurations that need to be maintained is smaller.
It is far easier to restore the environment in a disaster if you have all configuration and the scripts to install that configuration available.
The volume of change in things such as storage allocation, routing and VLANs is not the volume of change that an agile project sees. Good documentation is as solid a solution as configuration as code for something that changes rarely and the size/number of scripts and configurations that need to be maintained is smaller.
It is far easier to restore the environment in a disaster if you have all configuration and the scripts to install that configuration available.
Related Articles
Community Partners
DevOps Careers