If writing Terraform code that adheres to style conventions, how would you properly indent each nesting level compared to the one above it?

When writing Terraform code, proper indentation is crucial for readability and maintainability. Using two spaces for each nesting level aligns with common style conventions in Terraform, enhancing code clarity. This standard makes it easier for developers to visually differentiate between different blocks of code and nested resources.

Two spaces provide enough separation to indicate hierarchy without excessive whitespace that could lead to a cluttered appearance. Adhering to this convention also makes it easier for teams to collaborate on Terraform code, as consistent formatting can reduce misunderstandings and streamline the code review process.

While other options like using one space, four spaces, or tabs may be technically valid, they diverge from widely accepted best practices in the Terraform community and can introduce unnecessary complexity in reading and maintaining the code. Thus, using two spaces is the preferred method for indentation in Terraform.