Derek Ashmore , Application Transformation Principal , Asperitas , says that to thrive at DevOps , recognizing when you should not use IaC is just as critical as taking advantage of this methodology wherever it makes sense .

In a world where DevOps tooling has made it possible to automate virtually every process and workflow using an Infrastructure-as-Code ( IaC ) approach , deciding to take advantage of IaC at almost every opportunity is the obvious choice .

Instead , the question that really matters is “ what should we not manage via IaC ?”

In almost all businesses , there are some aspects of DevOps operations that teams shouldn ’ t handle through IaC – even if doing so is technically possible .

It ’ s not unusual to hear DevOps teams talk as if managing every process via IaC is their goal .

To explain this point , allow me to discuss the limitations of IaC-based automation and offer guidance on identifying processes that are not good candidates for IaC .

99 % vs 100 % Infrastructure-as-Code

In the context of DevOps , the value of Infrastructure-as- Code is obvious . Not only does configuring infrastructure

www . intelligentcio . com INTELLIGENTCIO LATAM 63