What is a practice of infrastructure as code?

Using multiple version control systems for the same infrastructure code would introduce unnecessary complexity and inconsistency, which contradicts IaC's goal of streamlined management.

While documentation is always useful, IaC strives for self-documenting code, where the code itself serves as the primary and most accurate documentation of the infrastructure's state, reducing the reliance on external documentation.

IaC defines infrastructure in a codified, repeatable manner, ensuring that deployments are consistent across development, staging, and production environments. This eliminates configuration drift and enforces a desired state, making deployments reliable and predictable.

Testing, integrating, and deploying once a day describes Continuous Integration/Continuous Deployment (CI/CD) practices, which are enabled by IaC but are not a practice of IaC itself; IaC defines *how* infrastructure is managed, not the frequency of deployment.