Difference between revisions of "Terraform workspaces"

Revision as of 09:05, 14 October 2022

Terraform workspaces 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

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.

Revision as of 09:05, 14 October 2022 (edit) Ant (talk \| contribs) ← Older edit		Revision as of 09:05, 14 October 2022 (edit) (undo) Ant (talk \| contribs) Newer edit →
Line 1:		Line 1:
−	[[Terraform workspaces]] allows to have multiple [[state files]] in the same working directory to manage multiple distinct sets of infrastructure resources.	+	Terraform workspaces allows to have multiple [[state files]] in the same working directory to manage multiple distinct sets of infrastructure resources.
	* https://www.terraform.io/language/state/workspaces		* https://www.terraform.io/language/state/workspaces