Difference between revisions of "Terraform workspaces"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
Tags: Mobile web edit, Mobile edit |
||
Line 21: | Line 21: | ||
== Related == | == Related == | ||
* <code>${terraform.workspace}</code> | * <code>${terraform.workspace}</code> | ||
+ | * [[Terraform provider: dns]] | ||
== See also == | == See also == |
Revision as of 22:35, 7 June 2022
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
- 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
terraform workspace new MY_NEW_WORKSPACE
terraform workspace select
terraform workspace list
terraform workspace show
terraform workspace delete
terraform workspace --help
Related
${terraform.workspace}
- Terraform provider: dns
See also
Advertising: