Last Updated on April 2, 2024 by Arnav Sharma

Terraform is an Infrastructure as Code (IaC) tool that allows you to build, change, and version infrastructure efficiently and will attempt to find the best configuration for a given environment. Terraform uses the HashiCorp Configuration Language (HCL), a domain-specific language that you’ll be familiar with if you’ve used other infrastructure automation tools, for defining and provisioning infrastructure across a variety of cloud and on-premises resources.

In Terraform, conditional logic can be applied using the if-else construct within expressions. However, unlike in many programming languages, Terraform doesn’t have traditional if-else control structures to direct the flow of execution. Instead, if-else logic in Terraform is implemented within expressions, primarily with the ternary operator, which follows the syntax: condition ? true_value : false_value.

Here’s an example of how you might use an if-else expression in Terraform to provision resources in Azure conditionally:

variable "deploy_environment" {
  description = "The environment to deploy into"
  type        = string
}

resource "azurerm_resource_group" "example" {
  # Resource group name is determined by the deploy_environment variable
  name     = var.deploy_environment == "production" ? "prod-rg" : "dev-rg"
  location = "East US"
}

resource "azurerm_virtual_network" "example" {
  # Virtual network name has a suffix based on the deploy_environment variable
  name                = "vnet-${var.deploy_environment == "production" ? "prod" : "dev"}"
  address_space       = ["10.0.0.0/16"]
  resource_group_name = azurerm_resource_group.example.name
  location            = azurerm_resource_group.example.location
}

output "resource_group_name" {
  value = azurerm_resource_group.example.name
}

In this example:

• The azurerm_resource_group resource’s name is set based on the value of the deploy_environment variable. If deploy_environment is "production", the name will be "prod-rg". Otherwise, it will be "dev-rg".
• The azurerm_virtual_network resource’s name includes a suffix that depends on whether deploy_environment equals "production" or not.

Remember that Terraform’s conditional expressions only work within the context of setting a value. You cannot use them to conditionally create resources. To conditionally create resources, you would use the count parameter or the for_each construct to control whether or not a resource is created based on your conditions.

Here’s an example with count:

resource "azurerm_storage_account" "example" {
  count               = var.deploy_environment == "production" ? 1 : 0
  name                = "prodstorageaccount"
  resource_group_name = azurerm_resource_group.example.name
  location            = azurerm_resource_group.example.location
  account_tier        = "Standard"
  account_replication_type = "GRS"
}

output "storage_account_name" {
  value = var.deploy_environment == "production" ? azurerm_storage_account.example[0].name : ""
}

In this count example:

• The azurerm_storage_account resource is only created if deploy_environment is "production". The count is set to 1 if the condition is true and 0 if false.
• The output storage_account_name will be the name of the storage account if created, or an empty string otherwise.

This approach to conditional logic allows you to create complex, conditional configurations in a declarative way, which is one of the strengths of Terraform.

FAQ – If else statement in Terraform

Q: How can I start using Terraform for my infrastructure needs?

A: To start using Terraform, first, you need general coding knowledge. Once you have that, look at the Terraform documentation and recommended articles from sources like Medium. They provide valuable insights into writing Terraform code and using Terraform modules effectively.

Q: What is a Terraform module and how is it used?

A: A Terraform module is a set of Terraform configurations grouped together for reuse. It’s a powerful tool that allows you to create multiple instances of similar infrastructure components. Modules make Terraform code more organized and maintainable, especially when dealing with multiple modules.

Q: Can Terraform integrate with Azure DevOps for infrastructure deployment?

A: Yes, Terraform can integrate seamlessly with Azure DevOps. This integration is beneficial for DevOps practices, allowing automated and consistent deployment of Terraform infrastructure across environments. Azure DevOps pipelines can be used to apply Terraform code, manage Terraform state, and ensure version control.

Q: How does Terraform handle conditional logic in its configurations?

A: Terraform uses a conditional expression syntax for handling logic. It supports an “if” statement and an “else statement in Terraform” for conditional configurations. This feature is especially useful when you need to conditionally configure resources based on certain conditions, like environment variables.

Q: What are the benefits of using Python with Terraform?

A: Combining Python with Terraform brings the best of both worlds: Python’s flexibility in scripting and Terraform’s capability in infrastructure as code. Python can be used to generate dynamic Terraform configurations, parse Terraform state files, or even automate certain aspects of Terraform workflows, leveraging its extensive library support.

Q: Is it possible to deploy Kubernetes clusters using Terraform?

A: Absolutely, Terraform can be used to deploy Kubernetes clusters. It offers a set of resources and modules specifically for Kubernetes, allowing you to define and manage your cluster’s configuration as code. This ensures that your Kubernetes infrastructure is reproducible, scalable, and maintainable.

Q: Can Terraform be used to manage cloud storage, like AWS S3 buckets?

A: Yes, Terraform can manage cloud storage solutions such as AWS S3 buckets. It allows you to define the configuration of the S3 bucket in code, including settings like bucket policies and object lifecycle management. This makes it easier to manage and version control your cloud storage infrastructure.

Q: What is the role of Terraform state, and why is it important?

A: The Terraform state file is a crucial component that tracks the state of your managed infrastructure and configurations. It records the current state of resources managed by Terraform, which Terraform uses to plan and apply changes. Managing the state file correctly is essential for accurate and reliable infrastructure management.

Q: How does Terraform handle dynamic blocks in its configuration?

A: Terraform’s dynamic block feature allows for the creation of repeatable nested blocks within a resource definition. This is useful when you need to create a list of similar resource attributes or configurations, as it avoids repetition and makes the code more concise and readable.

Q: What are some recommended practices for writing conditional expressions in Terraform?

A: When writing conditional expressions in Terraform, it’s recommended to clearly define defaults to replace invalid values and ensure that the condition is properly evaluated, whether it’s true or false. This helps in avoiding confusion as Terraform will attempt to make those conversions automatically.

Q: How does Terraform handle the deployment of resources in different environments like nonprod or prod?

A: In Terraform, you can use the var.environment parameter to specify the environment, such as nonprod or prod. Based on this, Terraform will dynamically deploy resources, such as an EC2 instance or an Azure resource, using conditional logic. For example, deploying 0 resources is also fine if the condition is not met for a specific environment.

Q: Can Terraform manage multiple cloud services, like Azure and AWS, within the same configuration?

A: Yes, Terraform can manage infrastructure across multiple cloud providers like Azure and AWS. You can define resources like an Azure VM or an AWS S3 bucket within the same Terraform configuration, using provider-specific modules and resources.

Q: How does for_each syntax enhance Terraform infrastructure management?

A: The for_each syntax in Terraform allows you to iterate over a list of resources or variables to create multiple instances of a resource. This is useful when you need to create a series of similar resources, such as multiple Azure VMs or AWS S3 buckets, without writing redundant code.

Q: What challenges might one face when using Kubernetes with Terraform, and how can they be addressed?

A: Integrating Kubernetes with Terraform can present a set of challenges, particularly around managing the lifecycle of Kubernetes resources and ensuring that configurations remain in sync. Addressing these challenges requires a solid understanding of both Kubernetes and Terraform, and possibly leveraging Terraform’s dynamic block feature to conditionally configure Kubernetes resources.

Q: In the context of DevOps, how important is having a background in general coding knowledge for using Terraform?

A: Having general coding knowledge is quite beneficial in the DevOps context, especially when using Terraform. It helps in understanding the syntax, writing effective code, and troubleshooting issues. This background enables more efficient and effective infrastructure automation and management.

Q: What is the role of Opentofu in relation to Terraform code and DevOps?

A: Opentofu could be a tool, platform, or methodology related to Terraform and DevOps. It might provide additional capabilities or integrations that enhance Terraform’s functionality in a DevOps pipeline, although further context is needed to specify its exact role.

Q: How does Terraform assist in creating a new reading list or documentation for infrastructure management?

A: Terraform itself doesn’t directly assist in creating a new reading list or documentation. However, the vast community around Terraform, including platforms like Medium, offers extensive documentation, tutorials, and articles that can be compiled into a new reading list for learning and managing infrastructure with Terraform.

terraform will attempt to find  checks if the variable terraform doesn’t support terraform does support traditional terraform if statement  resource to create cause confusion as  terraform input variable block in terraform hashicorp ambassador statement to deploy multiple attempt to find a type one resource