terraform

Description

Resolves a Terraform stack and either applies it automatically (if autoApply: true) or warns when the stack resources are not up-to-date.
Note: It is not recommended to set autoApply to true for any production or shared environments, since this may result in accidental or conflicting changes to the stack. Instead, it is recommended to manually plan and apply using the provided plugin commands. Run garden plugins terraform for details.
Stack outputs are made available as service outputs, that can be referenced by other modules under ${runtime.services.<module-name>.outputs.<key>}. You can template in those values as e.g. command arguments or environment variables for other services.
Note that you can also declare a Terraform root in the terraform provider configuration by setting the initRoot parameter. This may be preferable if you need the outputs of the Terraform stack to be available to other provider configurations, e.g. if you spin up an environment with the Terraform provider, and then use outputs from that to configure another provider or other modules via ${providers.terraform.outputs.<key>} template strings.
See the Terraform guide for a high-level introduction to the terraform provider.
Below is the full schema reference. For an introduction to configuring Garden modules, please look at our Configuration guide.
The first section contains the complete YAML schema, and the second section describes each schema key.
terraform modules also export values that are available in template strings. See the Outputs section below for details.

Complete YAML Schema

The values in the schema below are the default values.
1
# The schema version of this config (currently not used).
2
apiVersion: garden.io/v0
3
​
4
kind: Module
5
​
6
# The type of this module.
7
type:
8
​
9
# The name of this module.
10
name:
11
​
12
# Specify how to build the module. Note that plugins may define additional keys on this object.
13
build:
14
# A list of modules that must be built before this module is built.
15
dependencies:
16
- # Module name to build ahead of this module.
17
name:
18
​
19
# Specify one or more files or directories to copy from the built dependency to this module.
20
copy:
21
- # POSIX-style path or filename of the directory or file(s) to copy to the target.
22
source:
23
​
24
# POSIX-style path or filename to copy the directory or file(s), relative to the build directory.
25
# Defaults to to same as source path.
26
target: ''
27
​
28
# Maximum time in seconds to wait for build to finish.
29
timeout: 1200
30
​
31
# A description of the module.
32
description:
33
​
34
# Set this to `true` to disable the module. You can use this with conditional template strings to disable modules
35
# based on, for example, the current environment or other variables (e.g. `disabled: \${environment.name == "prod"}`).
36
# This can be handy when you only need certain modules for specific environments, e.g. only for development.
37
#
38
# Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also
39
# means that the module is not built _unless_ it is declared as a build dependency by another enabled module (in which
40
# case building this module is necessary for the dependant to be built).
41
#
42
# If you disable the module, and its services, tasks or tests are referenced as _runtime_ dependencies, Garden will
43
# automatically ignore those dependency declarations. Note however that template strings referencing the module's
44
# service or task outputs (i.e. runtime outputs) will fail to resolve when the module is disabled, so you need to make
45
# sure to provide alternate values for those if you're using them, using conditional expressions.
46
disabled: false
47
​
48
# Specify a list of POSIX-style paths or globs that should be regarded as the source files for this module. Files that
49
# do *not* match these paths or globs are excluded when computing the version of the module, when responding to
50
# filesystem watch events, and when staging builds.
51
#
52
# Note that you can also _exclude_ files using the `exclude` field or by placing `.gardenignore` files in your source
53
# tree, which use the same format as `.gitignore` files. See the [Configuration Files
54
# guide](https://docs.garden.io/using-garden/configuration-overview#including-excluding-files-and-directories) for
55
# details.
56
#
57
# Also note that specifying an empty list here means _no sources_ should be included.
58
include:
59
​
60
# Specify a list of POSIX-style paths or glob patterns that should be excluded from the module. Files that match these
61
# paths or globs are excluded when computing the version of the module, when responding to filesystem watch events,
62
# and when staging builds.
63
#
64
# Note that you can also explicitly _include_ files using the `include` field. If you also specify the `include`
65
# field, the files/patterns specified here are filtered from the files matched by `include`. See the [Configuration
66
# Files guide](https://docs.garden.io/using-garden/configuration-overview#including-excluding-files-and-directories)
67
# for details.
68
#
69
# Unlike the `modules.exclude` field in the project config, the filters here have _no effect_ on which files and
70
# directories are watched for changes. Use the project `modules.exclude` field to affect those, if you have large
71
# directories that should not be watched for changes.
72
exclude:
73
​
74
# A remote repository URL. Currently only supports git servers. Must contain a hash suffix pointing to a specific
75
# branch or tag, with the format: <git remote url>#<branch|tag>
76
#
77
# Garden will import the repository source code into this module, but read the module's config from the local
78
# garden.yml file.
79
repositoryUrl:
80
​
81
# When false, disables pushing this module to remote registries.
82
allowPublish: true
83
​
84
# A list of files to write to the module directory when resolving this module. This is useful to automatically
85
# generate (and template) any supporting files needed for the module.
86
generateFiles:
87
- # POSIX-style filename to read the source file contents from, relative to the path of the module (or the
88
# ModuleTemplate configuration file if one is being applied).
89
# This file may contain template strings, much like any other field in the configuration.
90
sourcePath:
91
​
92
# POSIX-style filename to write the resolved file contents to, relative to the path of the module source directory
93
# (for remote modules this means the root of the module repository, otherwise the directory of the module
94
# configuration).
95
#
96
# Note that any existing file with the same name will be overwritten. If the path contains one or more
97
# directories, they will be automatically created if missing.
98
targetPath:
99
​
100
# By default, Garden will attempt to resolve any Garden template strings in source files. Set this to false to
101
# skip resolving template strings. Note that this does not apply when setting the `value` field, since that's
102
# resolved earlier when parsing the configuration.
103
resolveTemplates: true
104
​
105
# The desired file contents as a string.
106
value:
107
​
108
# A map of variables to use when applying the stack. You can define these here or you can place a
109
# `terraform.tfvars` file in the working directory root.
110
#
111
# If you specified `variables` in the `terraform` provider config, those will be included but the variables
112
# specified here take precedence.
113
variables:
114
​
115
# If set to true, Garden will run `terraform destroy` on the stack when calling `garden delete env` or `garden delete
116
# service <module name>`.
117
allowDestroy: false
118
​
119
# If set to true, Garden will automatically run `terraform apply -auto-approve` when the stack is not
120
# up-to-date. Otherwise, a warning is logged if the stack is out-of-date, and an error thrown if it is missing
121
# entirely.
122
#
123
# **NOTE: This is not recommended for production, or shared environments in general!**
124
#
125
# Defaults to the value set in the provider config.
126
autoApply: null
127
​
128
# The names of any services that this service depends on at runtime, and the names of any tasks that should be
129
# executed before this service is deployed.
130
dependencies: []
131
​
132
# Specify the path to the working directory rootβ€”i.e. where your Terraform files areβ€”relative to the module root.
133
root: .
134
​
135
# The version of Terraform to use. Defaults to the version set in the provider config.
136
# Set to `null` to use whichever version of `terraform` that is on your PATH.
137
version:
138
​
139
# Use the specified Terraform workspace.
140
workspace:
Copied!

Configuration Keys

apiVersion

The schema version of this config (currently not used).
Type
Allowed Values
Default
Required
string
"garden.io/v0"
"garden.io/v0"
Yes

kind

Type
Allowed Values
Default
Required
string
"Module"
"Module"
Yes

type

The type of this module.
Type
Required
string
Yes
Example:
1
type: "container"
Copied!

name

The name of this module.
Type
Required
string
Yes
Example:
1
name: "my-sweet-module"
Copied!

build

Specify how to build the module. Note that plugins may define additional keys on this object.
Type
Default
Required
object
{"dependencies":[]}
No

build.dependencies[]

​build > dependencies
A list of modules that must be built before this module is built.
Type
Default
Required
array[object]
[]
No
Example:
1
build:
2
...
3
dependencies:
4
- name: some-other-module-name
Copied!

build.dependencies[].name

​build > dependencies > name
Module name to build ahead of this module.
Type
Required
string
Yes

build.dependencies[].copy[]

​build > dependencies > copy
Specify one or more files or directories to copy from the built dependency to this module.
Type
Default
Required
array[object]
[]
No

build.dependencies[].copy[].source

​build > dependencies > copy > source
POSIX-style path or filename of the directory or file(s) to copy to the target.
Type
Required
posixPath
Yes

build.dependencies[].copy[].target

​build > dependencies > copy > target
POSIX-style path or filename to copy the directory or file(s), relative to the build directory. Defaults to to same as source path.
Type
Default
Required
posixPath
""
No

build.timeout

​build > timeout
Maximum time in seconds to wait for build to finish.
Type
Default
Required
number
1200
No

description

A description of the module.
Type
Required
string
No

disabled

Set this to true to disable the module. You can use this with conditional template strings to disable modules based on, for example, the current environment or other variables (e.g. disabled: \${environment.name == "prod"}). This can be handy when you only need certain modules for specific environments, e.g. only for development.
Disabling a module means that any services, tasks and tests contained in it will not be deployed or run. It also means that the module is not built unless it is declared as a build dependency by another enabled module (in which case building this module is necessary for the dependant to be built).
If you disable the module, and its services, tasks or tests are referenced as runtime dependencies, Garden will automatically ignore those dependency declarations. Note however that template strings referencing the module's service or task outputs (i.e. runtime outputs) will fail to resolve when the module is disabled, so you need to make sure to provide alternate values for those if you're using them, using conditional expressions.
Type
Default
Required
boolean
false
No

include[]

Specify a list of POSIX-style paths or globs that should be regarded as the source files for this module. Files that do not match these paths or globs are excluded when computing the version of the module, when responding to filesystem watch events, and when staging builds.
Note that you can also exclude files using the exclude field or by placing .gardenignore files in your source tree, which use the same format as .gitignore files. See the Configuration Files guide for details.
Also note that specifying an empty list here means no sources should be included.
Type
Required
array[posixPath]
No
Example:
1
include:
2
- Dockerfile
3
- my-app.js
Copied!

exclude[]

Specify a list of POSIX-style paths or glob patterns that should be excluded from the module. Files that match these paths or globs are excluded when computing the version of the module, when responding to filesystem watch events, and when staging builds.
Note that you can also explicitly include files using the include field. If you also specify the include field, the files/patterns specified here are filtered from the files matched by include. See the Configuration Files guide for details.
Unlike the modules.exclude field in the project config, the filters here have no effect on which files and directories are watched for changes. Use the project modules.exclude field to affect those, if you have large directories that should not be watched for changes.
Type
Required
array[posixPath]
No
Example:
1
exclude:
2
- tmp/**/*
3
- '*.log'
Copied!

repositoryUrl

A remote repository URL. Currently only supports git servers. Must contain a hash suffix pointing to a specific branch or tag, with the format: #
Garden will import the repository source code into this module, but read the module's config from the local garden.yml file.
Type
Required
​
`gitUrl
string`
No
Example:
1
repositoryUrl: "git+https://github.com/org/repo.git#v2.0"
Copied!

allowPublish

When false, disables pushing this module to remote registries.
Type
Default
Required
boolean
true
No

generateFiles[]

A list of files to write to the module directory when resolving this module. This is useful to automatically generate (and template) any supporting files needed for the module.
Type
Default
Required
array[object]
[]
No

generateFiles[].sourcePath

​generateFiles > sourcePath
POSIX-style filename to read the source file contents from, relative to the path of the module (or the ModuleTemplate configuration file if one is being applied). This file may contain template strings, much like any other field in the configuration.
Type
Required
posixPath
No

generateFiles[].targetPath

​generateFiles > targetPath
POSIX-style filename to write the resolved file contents to, relative to the path of the module source directory (for remote modules this means the root of the module repository, otherwise the directory of the module configuration).
Note that any existing file with the same name will be overwritten. If the path contains one or more directories, they will be automatically created if missing.
Type
Required
posixPath
Yes

generateFiles[].resolveTemplates

​generateFiles > resolveTemplates
By default, Garden will attempt to resolve any Garden template strings in source files. Set this to false to skip resolving template strings. Note that this does not apply when setting the value field, since that's resolved earlier when parsing the configuration.
Type
Default
Required
boolean
true
No

generateFiles[].value

​generateFiles > value
The desired file contents as a string.
Type
Required
string
No

variables

A map of variables to use when applying the stack. You can define these here or you can place a terraform.tfvars file in the working directory root.
If you specified variables in the terraform provider config, those will be included but the variables specified here take precedence.
Type
Required
object
No

allowDestroy

If set to true, Garden will run terraform destroy on the stack when calling garden delete env or garden delete service <module name>.
Type
Default
Required
boolean
false
No

autoApply

If set to true, Garden will automatically run terraform apply -auto-approve when the 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!
Defaults to the value set in the provider config.
Type
Default
Required
boolean
null
No

dependencies[]

The names of any services that this service depends on at runtime, and the names of any tasks that should be executed before this service is deployed.
Type
Default
Required
array[string]
[]
No

root

Specify the path to the working directory rootβ€”i.e. where your Terraform files areβ€”relative to the module root.
Type
Default
Required
posixPath
"."
No

version

The version of Terraform to use. Defaults to the version set in the provider config. Set to null to use whichever version of terraform that is on your PATH.
Type
Required
string
No

workspace

Use the specified Terraform workspace.
Type
Required
string
No

Outputs

Module Outputs

The following keys are available via the ${modules.<module-name>} template string key for terraform modules.

${modules.<module-name>.buildPath}

The build path of the module.
Type
string
Example:
1
my-variable: ${modules.my-module.buildPath}
Copied!

${modules.<module-name>.name}

The name of the module.
Type
string

${modules.<module-name>.path}

The local path of the module.
Type
string
Example:
1
my-variable: ${modules.my-module.path}
Copied!

${modules.<module-name>.var.*}

A map of all variables defined in the module.
Type
Default
object
{}

${modules.<module-name>.var.<variable-name>}

Type
​
​
​
​
`string
number
boolean
link
array[link]`

${modules.<module-name>.version}

The current version of the module.
Type
string
Example:
1
my-variable: ${modules.my-module.version}
Copied!

Service Outputs

The following keys are available via the ${runtime.services.<service-name>} template string key for terraform module services. Note that these are only resolved when deploying/running dependants of the service, so they are not usable for every field.

${runtime.services.<service-name>.version}

The current version of the service.
Type
string
Example:
1
my-variable: ${runtime.services.my-service.version}
Copied!

${runtime.services.<service-name>.outputs.*}

A map of all the outputs defined in the Terraform stack.
Type
Default
object
{}

${runtime.services.<service-name>.outputs.<name>}

Type
​
​
​
​
`string
number
boolean
link
array[link]`

Task Outputs

The following keys are available via the ${runtime.tasks.<task-name>} template string key for terraform module tasks. Note that these are only resolved when deploying/running dependants of the task, so they are not usable for every field.

${runtime.tasks.<task-name>.version}

The current version of the task.
Type
string
Example:
1
my-variable: ${runtime.tasks.my-tasks.version}
Copied!
Last modified 18d ago