I'm a little confused by this comment. It feels like you are complaining about the problems that are solved by configuration management and infrastructure as code, yet you seem to reject it as too complicated.
All the problems you raise are solved by infrastructure as code.
Infrastructure as Code is literally is nothing more than keeping a config file in Git and running a script to apply the config to a REST API (or whatever). Terraform stands in as an overcomplicated script. Infrastructure as Code does not determine if what is being managed is immutable or not.
Configuration Management is a program designed to attempt to change mutable state so that it once again resembles what you want.
Immutable Infrastructure is immutable. You cannot change the state. Hence configuration management is pointless and unnecessary.
throwawaaarrgh|2 years ago
Infrastructure as Code is literally is nothing more than keeping a config file in Git and running a script to apply the config to a REST API (or whatever). Terraform stands in as an overcomplicated script. Infrastructure as Code does not determine if what is being managed is immutable or not.
Configuration Management is a program designed to attempt to change mutable state so that it once again resembles what you want.
Immutable Infrastructure is immutable. You cannot change the state. Hence configuration management is pointless and unnecessary.