Coding Conventions
A set of rules, techniques, and best practices for creating a cleaner, more readable, and more efficient code base with minimal errors. It helps future authors, as well as code reviewers, align.
Last updated
A set of rules, techniques, and best practices for creating a cleaner, more readable, and more efficient code base with minimal errors. It helps future authors, as well as code reviewers, align.
Last updated
The Terraform parser allows flexibility in laying out the elements in your configuration files. Still, the Terraform language also has some idiomatic style conventions, which we recommend users always follow for consistency between files and modules written by different teams.
You can enforce these conventions automatically by running terraform fmt
Understand the official Terraform configuration syntax.
Align with the official Terraform style conventions.
A block is a container for other content.
Providers: Terraform relies on " providers " plugins to interact with cloud providers, SaaS providers, and other APIs.
Data Sources: Data sources allow Terraform to use the information defined outside of Terraform, defined by another separate Terraform configuration, or modified by functions.
Modules: Modules are containers for multiple resources that are used together. A module consists of a collection of .tf files in a directory.
Resources: Resources are the most crucial element in the Terraform language. Each resource block describes one or more infrastructure objects, such as virtual networks, compute instances, or higher-level components, such as DNS records.
Variables in Terraform define reusable and configurable values to parameterize your configuration.
More straightforward Navigation: Finding variables becomes much faster, especially in large files, as they are easier to locate when sorted alphabetically.
Improved Readability: A consistent structure enhances readability for others working on the same code, making it easier to understand and maintain.
Reduced Errors: With variables organized, it's easier to spot duplicates or missing variables, minimizing potential errors.
Version Control: Alphabetical order reduces the likelihood of large, confusing diffs in version control systems, as only new variables appear where they belong.
Consistency Across Teams: It establishes a predictable format, improving team collaboration.
Clarity: Eliminates unnecessary repetition, making the code easier to understand.
Maintainability: Reducing redundancy helps simplify future updates and modifications. Changing a variable name once is more manageable than updating multiple instances of a repetitive name.
Modularity: Promotes better modular design, as variables are defined clearly within the context of the module, preventing confusion when modules are reused in different environments.
Consistency: Encourages clean, consistent naming conventions across modules, improving readability and making it easier for others to work with the code.
Clarity and Traceability: It clarifies where each variable comes from, mainly when multiple modules are used.
Avoiding Conflicts: Prevents naming conflicts between variables from different modules, reducing the risk of overwriting or misusing values.
Consistency in Large Projects: When dealing with large infrastructure projects, prefixed variable names help maintain a clean, organized structure, making it easier for teams to collaborate and manage the code.
Simplifies Debugging: Prefixing helps pinpoint the source of issues faster, as it’s easier to identify which module a variable belongs to when troubleshooting.
Improved Readability: In root modules, prefixed variables provide context at a glance, making the code more understandable for others working on the project.
