Writing all your configuration in code

We have seen throughout the book, especially with the first three chapters on IAC, that writing the desired infrastructure configuration in code offers many advantages for the productivity of both teams and the company.

It is, therefore, a very good practice to put everything related to infrastructure configuration in code. We have seen this in practice with Terraform, Ansible, and Packer, but many other tools exist that may be better suited to your needs and your organization. Among these tools, we are not only talking about the major editors, but also about the use of JavaScript Object Notation (JSON) files, Bash, PowerShell, and Python scripts that we'll apply to this configuration. The key is to have a description of your infrastructure in code that is easy for a human to read, and tools that are adapted to you, as discussed in the previous section.

Moreover, this practice continues to evolve in other fields, as we have seen in...