Re:Why is infrastructure as code such a big deal?
by tomvalorsa on Thursday July 16, 2020 @08:38AM
(#23858350)
I think consistency is a big benefit. Having the infrastructure described as code means that configurations are recorded in a uniform way (as opposed to just clicking around in a web interface to spin up resources and _maybe_ documenting it, for example). You can also check this code into source control and have a handle on how changes were made over time, which can be useful if a problem occurs and you want to isolate the change that broke your setup.
[ Parent
| on HN ]