From ab2dc0d9870f8a1a6c484d934ea433714ebbff85 Mon Sep 17 00:00:00 2001 From: Martin Atkins Date: Tue, 5 Dec 2017 09:07:16 -0800 Subject: [PATCH] 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. --- website/docs/commands/push.html.markdown | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/website/docs/commands/push.html.markdown b/website/docs/commands/push.html.markdown index 388f10a68f..ee667bce55 100644 --- a/website/docs/commands/push.html.markdown +++ b/website/docs/commands/push.html.markdown @@ -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