LogoLogo
Bonsai (0.13) DocsGitHubDiscord CommunityGarden Enterprise
Acorn (0.12)
Acorn (0.12)
  • Welcome!
  • 🌳Basics
    • How Garden Works
    • Quickstart Guide
    • The Stack Graph (Terminology)
  • 🌻Tutorials
    • Your First Project
      • 1. Initialize a Project
      • 2. Connect to a Cluster
      • 3. Deploy and Test
      • 4. Configure Your Project
  • 💐Using Garden
    • Configuration Overview
    • Projects
    • Modules
    • Services
    • Tests
    • Tasks
    • Workflows
    • Variables and templating
    • Module Templates
    • Using the CLI
  • 🌿Kubernetes Plugins
    • About
    • Remote K8s Plugin Configuration
      • 1. Create a Cluster
        • AWS
        • GCP
        • Azure
      • 2. Configure Container Registry (Optional)
        • AWS
        • GCP
        • Azure
      • 3. Set Up Ingress, TLS and DNS
      • 4. Configure the Provider
    • Local K8s Plugin Configuration
      • 1. Install Local Kubernetes
      • 2. Configure the Provider
    • Module Configuration
      • Container
      • Kubernetes
      • Helm
      • PersistentVolumeClaim
      • ConfigMap
    • Advanced
      • In-Cluster Building
      • Minimal RBAC Configuration for Development Clusters
      • Deploying to Production
  • 🌺Terraform Plugin
    • About
    • Provider Configuration
    • Module Configuration
  • ☘️Pulumi Plugin
    • About
    • Provider Configuration
    • Module Configuration
  • 🌹Other Plugins
    • Container
    • Exec (local scripts)
  • 🌼Guides
    • Installing Garden
    • Adopting Garden
    • Code Synchronization (Dev Mode)
    • Connecting a local service to a K8s cluster (Local Mode)
    • Environments and namespaces
    • Hot Reload
    • Migrating from Docker Compose to Garden
    • Using Garden in CI
  • 🌷Advanced
    • cert-manager Integration
    • Using Remote Sources
    • Custom Commands
  • 🪷Reference
    • Providers
      • conftest-container
      • conftest-kubernetes
      • conftest
      • container
      • exec
      • hadolint
      • jib
      • kubernetes
      • local-kubernetes
      • maven-container
      • octant
      • openfaas
      • pulumi
      • terraform
    • Module Types
      • configmap
      • conftest
      • container
      • exec
      • hadolint
      • helm
      • jib-container
      • kubernetes
      • maven-container
      • openfaas
      • persistentvolumeclaim
      • pulumi
      • templated
      • terraform
    • Template Strings
      • Project configuration context
      • Environment configuration context
      • Provider configuration context
      • Module configuration context
      • Remote Source configuration context
      • Project Output configuration context
      • Custom Command configuration context
      • Workflow configuration context
      • Template Helper Functions
    • Glossary
    • Commands
    • Project Configuration
    • Module Template Configuration
    • Workflow Configuration
  • 🎋Misc
    • FAQ
    • Troubleshooting
    • Telemetry
Powered by GitBook
On this page
  • Description
  • Complete YAML Schema
  • Configuration Keys
  • providers[]
  • providers[].name
  • providers[].dependencies[]
  • providers[].environments[]
  • providers[].allowDestroy
  • providers[].autoApply
  • providers[].initRoot
  • providers[].variables
  • providers[].version
  • providers[].workspace

Was this helpful?

  1. Reference
  2. Providers

terraform

PreviouspulumiNextModule Types

Last updated 1 year ago

Was this helpful?

Description

This provider allows you to integrate Terraform stacks into your Garden project. See the for details and usage information.

Below is the full schema reference for the provider configuration. For an introduction to configuring a Garden project with providers, please look at our .

The reference is divided into two sections. The contains the complete YAML schema, and the describes each schema key.

Complete YAML Schema

The values in the schema below are the default values.

providers:
  - # The name of the provider plugin to use.
    name:

    # List other providers that should be resolved before this one.
    dependencies: []

    # If specified, this provider will only be used in the listed environments. Note that an empty array effectively
    # disables the provider. To use a provider in all environments, omit this field.
    environments:

    # If set to true, Garden will run `terraform destroy` on the project root stack when calling `garden delete env`.
    allowDestroy: false

    # If set to true, Garden will automatically run `terraform apply -auto-approve` when a stack is not up-to-date.
    # Otherwise, a warning is logged if the stack is out-of-date, and an error thrown if it is missing entirely.
    #
    # **Note: This is not recommended for production, or shared environments in general!**
    autoApply: false

    # Specify the path to a Terraform config directory, that should be resolved when initializing the provider. This
    # is useful when other providers need to be able to reference the outputs from the stack.
    #
    # See the [Terraform guide](https://docs.garden.io/v/acorn-0.12/advanced/terraform) for more information.
    initRoot:

    # A map of variables to use when applying Terraform stacks. You can define these here, in individual
    # `terraform` module configs, or you can place a `terraform.tfvars` file in each working directory.
    variables:

    # The version of Terraform to use. Set to `null` to use whichever version of `terraform` that is on your PATH.
    version: 1.2.9

    # Use the specified Terraform workspace.
    workspace:

Configuration Keys

providers[]

Type
Default
Required

array[object]

[]

No

providers[].name

The name of the provider plugin to use.

Type
Required

string

Yes

Example:

providers:
  - name: "local-kubernetes"

providers[].dependencies[]

List other providers that should be resolved before this one.

Type
Default
Required

array[string]

[]

No

Example:

providers:
  - dependencies:
      - exec

providers[].environments[]

If specified, this provider will only be used in the listed environments. Note that an empty array effectively disables the provider. To use a provider in all environments, omit this field.

Type
Required

array[string]

No

Example:

providers:
  - environments:
      - dev
      - stage

providers[].allowDestroy

If set to true, Garden will run terraform destroy on the project root stack when calling garden delete env.

Type
Default
Required

boolean

false

No

providers[].autoApply

If set to true, Garden will automatically run terraform apply -auto-approve when a stack is not up-to-date. Otherwise, a warning is logged if the stack is out-of-date, and an error thrown if it is missing entirely.

Note: This is not recommended for production, or shared environments in general!

Type
Default
Required

boolean

false

No

providers[].initRoot

Specify the path to a Terraform config directory, that should be resolved when initializing the provider. This is useful when other providers need to be able to reference the outputs from the stack.

Type
Required

posixPath

No

providers[].variables

A map of variables to use when applying Terraform stacks. You can define these here, in individual terraform module configs, or you can place a terraform.tfvars file in each working directory.

Type
Required

object

No

providers[].version

The version of Terraform to use. Set to null to use whichever version of terraform that is on your PATH.

Type
Allowed Values
Default
Required

string

"0.12.26", "0.13.3", "0.14.7", "1.0.5", "1.2.9", null

"1.2.9"

Yes

providers[].workspace

Use the specified Terraform workspace.

Type
Required

string

No

> name

> dependencies

> environments

> allowDestroy

> autoApply

> initRoot

See the for more information.

> variables

> version

> workspace

🪷
Terraform guide
Terraform guide
configuration guide
first section
second section
providers
providers
providers
providers
providers
providers
providers
providers
providers