Difference between revisions of "Remote state backends to manage Terraform state"

From wikieduonline
Jump to navigation Jump to search
Line 14: Line 14:
 
   backend "s3" {
 
   backend "s3" {
 
     bucket = "my-terraform-states"
 
     bucket = "my-terraform-states"
     key    = "terraform[[.tfstate]]"
+
     key    = "path/to/not/override/other/terraform[[.tfstate]]"
 
     region = "us-west-2"
 
     region = "us-west-2"
 
     [[dynamodb_table]] = "my-terraform-states-table"
 
     [[dynamodb_table]] = "my-terraform-states-table"

Revision as of 19:21, 21 October 2021

# stage/frontend-app/main.tf
terraform {
  backend "s3" {
    bucket         = "my-terraform-state"
    key            = "stage/frontend-app/terraform.tfstate"
    region         = "us-east-1"
    encrypt        = true
    dynamodb_table = "my-lock-table"
  }
}


terraform {
  backend "s3" {
    bucket = "my-terraform-states"
    key    = "path/to/not/override/other/terraform.tfstate"
    region = "us-west-2"
    dynamodb_table = "my-terraform-states-table"
    profile = "your_profile"
    workspace_key_prefix = "your-prefix"
  }


GitLab 13.0 (2020) can be used as an HTTP backend for Terraform.

terraform {
  backend "http" {}
}


See also

Advertising: