Website: 0.14 Upgrade guide additions (#27112)

* Update 0-14.html.markdown

Spelling again. Thanks @pselle
This commit is contained in:
Petros Kolyvas 2020-12-03 14:21:31 -04:00 committed by GitHub
parent 0c0749edcf
commit 20a5db1c86
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 0 deletions

View File

@ -49,6 +49,7 @@ Upgrade guide sections:
* [Provider Dependency Lock File](#provider-dependency-lock-file) * [Provider Dependency Lock File](#provider-dependency-lock-file)
* [Concise Terraform Plan Output](#concise-terraform-plan-output) * [Concise Terraform Plan Output](#concise-terraform-plan-output)
* [Sensitive Values in Plan Output](#sensitive-values-in-plan-output) * [Sensitive Values in Plan Output](#sensitive-values-in-plan-output)
* [Other important workflow changes](#other-changes)
## Before You Upgrade ## Before You Upgrade
@ -404,3 +405,14 @@ may cause those values to become visible to others.
Sensitive values are also still saved in state snapshots stored in your Sensitive values are also still saved in state snapshots stored in your
configured backend. Use the access control and audit mechanisms offered by configured backend. Use the access control and audit mechanisms offered by
the remote system to control who can access that data. the remote system to control who can access that data.
## Other Important Workflow Changes
### Terraform Output Formatting
We've modified the formatting of `terraform output` to match the formatting of `terraform show`.
We consider the console output of Terraform human readable; specifically designed and optimized for operators and practitioners to review themselves. As a result we occasionally (maybe even regularly) intend to tweak that output to help improve consistently, clarity, actionability and more.
If you rely on `terraform output` in automation, please use `terraform output -json`.