When Configuration Management Becomes an Operational Liability
Configuration management rarely becomes a liability because it cannot run a command. It becomes a liability when successful command execution is mistaken for operational control.
Ansible is flexible enough to create a cloud resource, build an image, launch a migration, rotate a password, or promote a database. That flexibility makes it easy to keep adding responsibilities until a playbook becomes the resource ledger, runtime controller, artifact system, credential authority, and approval workflow.
The playbook may finish green while responsibility for state, recovery, or the next decision remains unclear. At that point, more automation has created less control.
Choosing not to use Ansible for a particular operation is not a rejection of configuration management. Different infrastructure problems require different control models. The important question is not whether Ansible can call the necessary command or API, but which system must remain responsible after the call.
Start With the Control Model
An Ansible...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
