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

website: "terraform push" version matching requirement 

It's important to match the version of local Terraform with the remote Terraform version in Terraform Enterprise when using the "terraform push" command, or else the uploaded configuration package may not be compatible.
This commit is contained in:
Martin Atkins 2017-12-05 09:07:16 -08:00
parent 44cb98e04f
commit ab2dc0d987
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
website/docs/commands/push.html.markdown
View File

@ -25,6 +25,11 @@ future update of Terraform Enterprise will allow parallel Terraform runs and aut
perform infrastructure locking so only one run is modifying the same
infrastructure at a time.
~> When using this command, it is important to match your local Terraform version with
the version selected for the target workspace in Terraform Enterprise, since
otherwise the uploaded configuration archive may not be compatible with the remote
Terraform process.
## Usage
Usage: `terraform push [options] [path]`
@ -90,6 +95,13 @@ all the files to be safe. To exclude certain files, specify the `-exclude`
flag when pushing, or specify the `exclude` parameter in the
[Terraform Enterprise configuration section](/docs/configuration/terraform-enterprise.html).
Terraform also includes in the package all of the modules that were installed
during the most recent `terraform init` or `terraform get` command. Since the
details of how modules are cached in the filesystem vary between Terraform versions,
it is important to use the same version of Terraform both locally (when running
`terraform init` and then `terraform push`) and in your remote Terraform Enterprise
workspace.
## Terraform Variables
When you `push`, Terraform will automatically set the local values of