Fix content for terraform and aws roadmaps (#7589)
* Fix URLs to AWS docs: links pointed to portuguese version of documentation * Fix URL to official process.env documentation (it pointed to an unrelated digital ocean article about command line args) * Fix typo * Add resource lifecycle node * Fix @article@ tag case * * Fix common but dangerous misconception: values, even if marked as sensitive, ARE written to state files in CLEAR text! * Source: https://developer.hashicorp.com/terraform/language/values/outputs#sensitive-suppressing-values-in-cli-output * Fix minor display issue: "<sensitive>" is rendered to "", so it was changed to `<sensitive>` * Fix missing space * Update terraform plan & apply * Fix link to terraform apply docs (pointed to terraform plan) * Add link to official terraform plan docs to terraform plan nodepull/7591/head
parent
5933413f3b
commit
4910719d4e
13 changed files with 27 additions and 13 deletions
@ -1 +1,14 @@ |
||||
# Resource Lifecycle |
||||
|
||||
Each Terraform resource is subject to the lifecycle: Create, Update or Recreate, Destroy. When executing `terraform apply`, each resource: |
||||
* which exists in configuration but not in state is created |
||||
* which exists in configuration and state and has changed is updated |
||||
* which exists in configuration and state and has changed, but cannot updated due to API limitation is destroyed and recreated |
||||
* which exists in state, but not (anymore) in configuration is destroyed |
||||
|
||||
The lifecycle behaviour can be modified to some extend using the `lifecycle` meta argument. |
||||
|
||||
Learn more from the following resources: |
||||
|
||||
- [@official@How Terraform Applies a Configuration](https://developer.hashicorp.com/terraform/language/resources/behavior#how-terraform-applies-a-configuration) |
||||
- [@official@The lifecycle Meta-Argument](https://developer.hashicorp.com/terraform/language/meta-arguments/lifecycle) |
Loading…
Reference in new issue