Why I don’t prefer using Terraform, Ansible, Puppet, and other tools for defining Infrastructure as Code (aC)

In the world of Infrastructure as Code (IaC), many powerful tools like Terraform, Ansible, and Puppet are available to automate and manage infrastructure. These tools help make infrastructure definitions easily manageable, versionable, and automatable. However, when we look at aC (as Code), the answer for me is not just about how to reach the desired state, but also how to validate that state consistently — not just for infrastructure, but for any system that can be automatically managed, including applications, security, and platforms.

Why don’t I use the traditional tools?

The answer is simple but not straightforward. Tools like Terraform, Ansible, and Puppet each excel in their specific areas, but each focuses on a particular part of the process. In IaC, these tools work well when automating specific aspects of infrastructure. But when applied in the context of aC, achieving the main goal — a unified description and validation of the different system domains — becomes difficult without significantly altering the base concepts of these tools.

Why? Because Terraform, Ansible, and similar tools typically focus on specific functions, and they aren’t designed to manage all the necessary components in an integrated way. What we need is a solution that not only defines each component but also provides the necessary validation and checks between them. This would ensure the correct relationships and functionality between all system components.

The Solution: Modern Tools and a Unified Validation System

For me, the solution is handling the management of platforms, applications, and other components through a unified validation system. This toolset ensures that not only are the desired states described, but they are also validated effectively.

In the world of aC, the key is to not just describe the desired state, but to have automated validation. This is especially crucial considering the complexity of modern applications and infrastructures, as well as the dynamic changes they undergo continuously.

Why is validation important?

Validation is crucial because the applied tools and configurations ensure that aC definitions work as expected. By continuously checking and validating the desired state, we can maintain consistent and reliable operation across all components.

So, the answer isn't "why don't I use Terraform, Ansible, or Puppet", but rather, "why is there a need for a new approach that integrates all aC types into one unified validation system?" This system guarantees the creation of flexible, sustainable, and scalable solutions without forcing the core tool concepts to be compromised.

#IaC#DevOps#CloudNative#Automation#InfrastructureAsCode