Difference between revisions of "Remote state backends to manage Terraform state"
Jump to navigation
Jump to search
(Created page with " <pre> # stage/frontend-app/main.tf terraform { backend "s3" { bucket = "my-terraform-state" key = "stage/frontend-app/terraform.tfstate" reg...") |
|||
Line 13: | Line 13: | ||
} | } | ||
</pre> | </pre> | ||
+ | |||
+ | |||
+ | GitLab 13.0 (2020) can be used as an [[HTTP]] backend for Terraform. | ||
Revision as of 08:12, 14 March 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" } }
GitLab 13.0 (2020) can be used as an HTTP backend for Terraform.
See also
- Terraform, OpenTofu, Terrakube.org, Installation, Terraform AWS, Terraform GCP, Terraform commands, Terraform Cloud, Terraform Enterprise (TFE), HCL, HIL, meta-arguments, providers, modules, resource, provisioners, data sources, backends: remote backends, examples, configuration files, state files, variables, types, Terraform Registry, conditionals:
depends_on
, functions, Blocks, dynamic blocks, errors, Terragrunt, Terraformer, Terratest, Terraform certifications, Terraform map type, Terraform Associate, Terraform: list type,TF_VAR_, TF_LOG
, Terraform provider versioning, Terraform Style Conventions, Required version, Terraform plugin, Terraform Named Values, tags, Changelog,tfsec, tflint
, Operators, Expressions:for, splat
, Debugging, Namespaces, Terraform Landing Zones, CDKTF, Atmos
Advertising: