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

# When to use Terraform workspaces

Terraform workspaces are commonly used in large organizations to delegate responsibilities and roles to different team members. Each team would be granted permission to perform updates on workspaces related to their role. Additionally, production and staging type environments may have different permissions applied to their workspaces to further restrict who can deploy updates to these sensitive environments.

The `current workspace` name is stored locally in the `.terraform` directory. This allows multiple team members to work in different workspaces concurrently.

# Types of workspaces

Let’s assume we’re working in a large organization. In this organization, there’s a networking team, a governance team, and an application team. There are also multiple environment types, like production, staging, and development.

Each team is responsible for its own Terraform configurations that create and manage their respective components. In order to separate roles and permissions across all environments and configurations, we could create the following workspaces:

* `networking-dev`
* `networking-stage`
* `networking-prod`
* `governance-dev`
* `governance-stage`
* `governance-prod`
* `application-dev`
* `application-stage`
* `application-prod`

This will keep each team’s work separate (even if it’s contained in the same repository) and allow for independent progression through the development and staging of changes.

Learn when to use Terraform workspaces and their types.

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

Using Workspaces

When to use Terraform workspaces