Skip to main content

Documentation Index

Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt

Use this file to discover all available pages before exploring further.

In this lesson, we explore the structure and naming conventions of the Terraform configuration directory to optimize project organization and enhance configuration management. Previously, we worked with a single configuration file named local.tf located in the terraform-local-file directory. Below is an example demonstrating how to list the files in this directory along with the contents of local.tf: 
[terraform-local-file]$ ls /root/terraform-local-file
local.tf

resource "local_file" "pet" {
  filename = "/root/pets.txt"
  content  = "We love pets!"
}
Terraform supports splitting configuration across multiple files. For instance, you can create an additional file named cat.tf that introduces a new resource using the same local_file provider: 
[terraform-local-file]$ ls /root/terraform-local-file
local.tf  # Note: cat.tf is now also present in the directory.

resource "local_file" "cat" {
  filename = "/root/cat.txt"
  content  = "My favorite pet is Mr. Whiskers"
}
When you apply your configuration, Terraform automatically processes every file in the directory with the .tf extension. This ensures that both pets.txt and cat.txt will be created as specified.
It is also common practice to consolidate resource definitions into one configuration file, often named main.tf. To further organize your configuration, you can use additional files such as:
FilePurpose
variables.tfTo define input variables
outputs.tfTo specify outputs for the configuration
providers.tfTo configure provider settings
These topics will be discussed in detail later in the lesson. Now, let’s continue with practical exercises to explore working with providers.

Watch Video

Practice Lab