When should I use this Terraform workflow?

Use it when provisioning cloud infrastructure, creating Terraform modules, managing multi-environment infrastructure, implementing IaC best practices, or setting up Terraform workflows. It's not needed for infrastructure managed by different IaC tools or single ad hoc resources that don't warrant full module, remote-state, and CI/CD setup.

What skills are involved in the State Management phase?

The State Management phase uses `terraform-specialist` to configure a remote backend, state locking, workspaces, state access, and backup.

Does this workflow include CI/CD and security setup?

Yes, the CI/CD Integration phase uses `cicd-automation-workflow-automate` and `github-actions-templates` to create a CI pipeline with plan/apply steps, approvals, and validation. The Security phase uses `secrets-management` and `terraform-specialist` to configure secrets, encryption, policies, compliance, and access auditing.

Skill

Orchestrate Terraform Infrastructure Deployments

Name: Terraform Infrastructure Workflow
Availability: OnlineOnly
Author: Antigravity

Seven-phase Terraform workflow covering provisioning, modules, state management, multi-environment, CI/CD, and security.

Get skill

Works with terraform github

Antigravity

Own this? Claim it

Spark score

out of 100

Updated last month

Version 13.1.1

Add to Favorites

Why it matters

Automate your infrastructure as code with a comprehensive Terraform workflow. This asset handles resource provisioning, module creation, state management, and multi-environment deployments, ensuring robust and scalable cloud infrastructure.

Outcomes

What it gets done

Provision cloud resources using Terraform modules.

Create reusable Terraform modules with defined interfaces.

Manage Terraform state securely with remote backends and locking.

Integrate Terraform into CI/CD pipelines for automated deployments.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-terraform-infrastructure | bash

Overview

Terraform Infrastructure Workflow

A seven-phase Terraform infrastructure-as-code workflow covering setup, resource provisioning, module creation, state management, multi-environment deployment, CI/CD integration, and security, each paired with specific skills and a quality-gate checklist. Use when provisioning cloud infrastructure, creating Terraform modules, or setting up multi-environment or CI/CD Terraform workflows; not needed for a single ad hoc resource.

What it does

Specialized 7-phase workflow for infrastructure as code with Terraform, covering resource provisioning, module creation, state management, and multi-environment deployments, in order: Terraform Setup, Resource Provisioning, Module Creation, State Management, Multi-Environment, CI/CD Integration, and Security. Each phase names the specific skills to invoke and a concrete action sequence, rather than leaving Terraform usage to general knowledge.

When to use - and when NOT to

Use this when provisioning cloud infrastructure, creating Terraform modules, managing multi-environment infrastructure, implementing IaC best practices, or setting up Terraform workflows.

Not needed for infrastructure managed by a different IaC tool, or for a single ad hoc resource that doesn't warrant the overhead of a full module, remote-state, and CI/CD setup.

Inputs and outputs

Each phase pairs skills with an action sequence. Terraform Setup (terraform-skill, terraform-specialist) initializes Terraform, configures the backend and providers, and sets up variables and outputs. Resource Provisioning (terraform-module-library, cloud-architect) designs infrastructure, creates resource definitions, and configures networking, compute, and storage. Module Creation (terraform-module-library) designs a module interface and structure, defines variables and outputs, adds documentation, and tests the module. State Management (terraform-specialist) configures a remote backend, state locking, workspaces, state access, and backup.

Use @terraform-skill to set up Terraform project

Sample copy-paste prompts for the other phases follow the same pattern: "Use @terraform-module-library to provision cloud resources", "Use @terraform-module-library to create reusable Terraform module", "Use @terraform-specialist to configure Terraform state", "Use @terraform-specialist to set up multi-environment Terraform", "Use @cicd-automation-workflow-automate to create Terraform CI/CD", and "Use @secrets-management to secure Terraform secrets".

Integrations

Multi-Environment (terraform-specialist) designs environment structure, creates per-environment configs and variable files, configures isolation, and tests deployments. CI/CD Integration (cicd-automation-workflow-automate, github-actions-templates) creates a CI pipeline with plan/apply steps, approvals, and validation, then tests it. Security (secrets-management, terraform-specialist) configures secrets, encryption, policies, compliance, and access auditing. A quality-gate checklist verifies, item by item, that resources are provisioned, modules are working, state is configured, multi-environment setups are tested, CI/CD is working, and security has been verified before the infrastructure is considered done. Related workflow bundles: cloud-devops for cloud and DevOps work, kubernetes-deployment, and aws-infrastructure for AWS-specific patterns.

Who it's for

Platform and DevOps engineers setting up Terraform infrastructure end to end - provisioning, modules, state, multi-environment, CI/CD, and security - who need a structured, phase-by-phase workflow with named skills and copy-paste prompts for each step, rather than ad hoc Terraform usage pieced together on the fly.

FAQ

Common questions

Discussion