Editing Terraform state files
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 18: | Line 18: | ||
* <code>[[Terraform S3 backend|key]]</code> in [[Terraform S3 backend]] | * <code>[[Terraform S3 backend|key]]</code> in [[Terraform S3 backend]] | ||
* [[Terraform Associate]]: Understand [[secret management]] in [[state files]] | * [[Terraform Associate]]: Understand [[secret management]] in [[state files]] | ||
− | * <code>[[.terraform.lock.hcl]] | + | * <code>[[.terraform.lock.hcl]] (Generated executing: <code>[[terraform init]]</code>)</code> |
* <code>[[terraform workspace]]</code> | * <code>[[terraform workspace]]</code> | ||
* [[Terraform Cloud]]: [[Controlled remote state Access]] (May 2021<ref>https://www.hashicorp.com/blog/announcing-controlled-remote-state-access-for-terraform-cloud-and-enterprise</ref>) feature in [[Terraform Cloud]] and Terraform Enterprise, users now have a new way to establish granular controls for [[state ]] accessibility. | * [[Terraform Cloud]]: [[Controlled remote state Access]] (May 2021<ref>https://www.hashicorp.com/blog/announcing-controlled-remote-state-access-for-terraform-cloud-and-enterprise</ref>) feature in [[Terraform Cloud]] and Terraform Enterprise, users now have a new way to establish granular controls for [[state ]] accessibility. |
Advertising: