Difference between revisions of "Terraform workspaces"
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
* https://www.terraform.io/language/state/workspaces | * https://www.terraform.io/language/state/workspaces | ||
| − | |||
Certain [[backends]] support multiple named workspaces allowing multiple states to be associated with a single configuration. | Certain [[backends]] support multiple named workspaces allowing multiple states to be associated with a single configuration. | ||
| Line 22: | Line 21: | ||
== Related == | == Related == | ||
| − | * <code>${terraform.workspace}</code> | + | * <code>${[[terraform.workspace]]}</code> |
* [[Terraform provider: dns]] | * [[Terraform provider: dns]] | ||
| + | * [[Terragrunt]] | ||
== See also == | == See also == | ||
Latest revision as of 19:03, 15 July 2024
Terraform workspaces (Mar 2017, previously known as State Environments ) allows to have multiple state files in the same working directory to manage multiple distinct sets of infrastructure resources.
Certain backends support multiple named workspaces allowing multiple states to be associated with a single configuration.
- Supported backends: AzureRM, Consul, COS, etcdv3, GCS, Kubernetes, Local, Manta, OSS, Postgres, Remote, S3, Swift
Contents
Usage scenarios[edit]
- To create a parallel, distinct copy of a set of infrastructure in order to test a set of changes before modifying the main production infrastructure.
- Non-default workspaces are often related to feature branches in version control.
Commands[edit]
terraform workspace new MY_NEW_WORKSPACEterraform workspace selectterraform workspace listterraform workspace showterraform workspace deleteterraform workspace --help
Related[edit]
See also[edit]
Advertising:
