Open RafiGreenberg opened 5 years ago
Same problem here.
I see that between last terraform plan and current terraform plan, versions for template and null providers have increased from 1.0.0 to 2.0.0:
diff -u terraform_plan_head_last.txt terraform_plan_head_current.txt 1 ↵
--- terraform_plan_head_last.txt 2019-01-28 12:09:42.696464906 +0100
+++ terraform_plan_head_current.txt 2019-01-28 12:09:15.448195800 +0100
@@ -20,8 +20,8 @@
- Checking for available provider plugins on https://releases.hashicorp.com...
- Downloading plugin for provider "google" (1.20.0)...
- Downloading plugin for provider "vault" (1.4.1)...
-- Downloading plugin for provider "template" (1.0.0)...
-- Downloading plugin for provider "null" (1.0.0)...
+- Downloading plugin for provider "null" (2.0.0)...
+- Downloading plugin for provider "template" (2.0.0)...
The following providers do not have any version constraints in configuration,
so the latest version was installed.
@@ -32,6 +32,6 @@
suggested below.
* provider.google: version = "~> 1.20"
-* provider.null: version = "~> 1.0"
-* provider.template: version = "~> 1.0"
+* provider.null: version = "~> 2.0"
+* provider.template: version = "~> 2.0"
* provider.vault: version = "~> 1.4"
I also see that the old init script is different from new init script, but I'm not sure if that's the root cause:
diff -u init_script_{old,new}.sh 127 ↵
--- init_script_old.sh 2019-01-28 12:03:51.893538189 +0100
+++ init_script_new.sh 2019-01-28 12:04:03.301610886 +0100
@@ -15,7 +15,7 @@
ENABLE_SQUID="false"
-if [[ "$ENABLE_SQUID" == "true" ]]; then
+if [[ "$$ENABLE_SQUID" == "true" ]]; then
apt-get install -y squid3
cat - > /etc/squid/squid.conf <<'EOM'
How can we resolve the problem ?
On release 1.2.2 (and also tested downgrading to 1.2.1 and 1.2.0), I'm getting "forces new resource" for multiple resources when attempting to plan/apply:
Terraform v0.11.11