ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

website: clarify in legacy upgrade that we support k/v on init

This commit is contained in:
Mitchell Hashimoto 2017-03-17 16:03:25 -07:00
parent 1d1dc7cf30
commit 1b4fda0e1e
No known key found for this signature in database
GPG Key ID: 744E147AA52F5B0A
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
website/source/docs/backends/legacy-0-8.html.md
View File

@ -118,12 +118,15 @@ and you will lose any changes that were in the remote location.
The `terraform remote config` command has been replaced with The `terraform remote config` command has been replaced with
`terraform init`. The new command is better in many ways by allowing file-based `terraform init`. The new command is better in many ways by allowing file-based
configuration, automatic state migration, and more. However, the new configuration, automatic state migration, and more.
command doesn't support configuration via command-line flags.
You should be able to very easily migrate `terraform remote config`
scripting to the new `terraform init` command.
The new `terraform init` command takes a `-backend-config` flag which is The new `terraform init` command takes a `-backend-config` flag which is
an HCL file that is merged with the backend configuration in your Terraform eitheran HCL file or a string in the format of `key=value`. This configuration
files. This lets you keep secrets out of your actual configuration. is merged with the backend configuration in your Terraform files.
This lets you keep secrets out of your actual configuration.
We call this "partial configuration" and you can learn more in the We call this "partial configuration" and you can learn more in the
docs on [configuring backends](/docs/backends/config.html). docs on [configuring backends](/docs/backends/config.html).