Gain insights into Infrastructure as Code with Terraform, sharpen your skills, and prepare for the HashiCorp Terraform Associate certification in a cloud-agnostic way.

HashiCorp Terraform Certified Associate Preparation Guide.png

Terraform_e.tar.gz

access_key_id

secret_access_key

init

validate

config

needed-copy

not-needed-copy

needed-copy-copy

This course is designed to help learners obtain the Terraform Associate certification from HashiCorp. 

You’ve likely picked up this course because you dabbled in Terraform as a hobbyist or in a
development environment, and you’re excited about the possibilities of deploying Infrastructure 
as Code (IaC). It will enable you to sharpen your skills and prove your knowledge with a certification from HashiCorp. Terraform is an amazing tool to deploy Infrastructure as Code in a cloud-agnostic way. We’re excited to share our accumulated knowledge with you through this course.

HashiCorp Terraform Certified Associate Preparation Guide

# Configuring inputs and outputs for modules

We can configure inputs and outputs for modules with an API interface. This allows us to customize them for specific requirements while our code remains as DRY and reusable as possible.

Every directory containing configuration is automatically a module in Terraform. Using modules just means explicitly referencing that configuration. References to modules are created with the `module` block, and resources created by the child module are exposed through outputs defined in the child module.


# Scope of a local value

A local value defined in a module is only available in the context of that module. The calling module and any other child modules invoked by that calling module don’t have access to those local values unless they’re exposed as output values. For instance, let’s say we  have a root module that invokes two child modules, A and B. Any local values created in module A won’t be available to the root module or module B.

# Scope of variables within a module

Variables are contained within a module. If we’re calling a module, however, we also need to pass values for any variables that don’t have a default value as part of that module call. Those are the inputs for the module.

# Scope of variables within a child module

The child module doesn’t have access to variables defined in the calling module unless they’re explicitly passed as inputs. For instance, let’s say we have a root module with a variable called`naming_prefix`. 


Learn the scope of local values, variables, and outputs within modules and child modules.


Variable Scope within Modules and Child Modules

Learn the scope of local values, variables, and outputs within modules and child modules.

Introduction to the Course

Introduction to Infrastructure as Code

Basics of Terraform

Outside the Workflow: Using the Terraform CLI

Terraform Modules

Navigate Terraform Workflow

Implement and Maintain State

Read, Generate, and Modify Configuration

Understand Terraform Enterprise Capabilities

Conclusion

Variable Scope within Modules and Child Modules

Configuring inputs and outputs for modules