terraform plan or maybe refresh removes outputs from state file

[bitglue]

If you have a configuration that uses modules which have outputs, or the root module has outputs of its own, terraform plan will eat them.

diff --git a/state/terraform.tfstate b/state/terraform.tfstate
index 8ce953a..287af53 100644
--- a/state/terraform.tfstate
+++ b/state/terraform.tfstate
@@ -1,17 +1,12 @@
 {
     "version": 1,
-    "serial": 54,
+    "serial": 55,
     "modules": [
         {
             "path": [
                 "root"
             ],
-            "outputs": {
-                "dev_public_ip": "xxx",
-                "dev_vpc_id": "vpc-xxx",
-                "internal_public_ip": "xxx",
-                "internal_vpc_id": "vpc-xxx"
-            },
+            "outputs": {},
             "resources": {}
         },
         {
Stage this hunk [y,n,q,a,d,/,j,J,g,s,e,?]? y
@@ -19,12 +14,7 @@
                 "root",
                 "dev_coreos"
             ],
-            "outputs": {
-                "public_ip": "xxx",
-                "subnet_id_0": "subnet-xxx",
-                "subnet_id_1": "subnet-xxx",
-                "subnet_id_2": "subnet-xxx"
-            },
+            "outputs": {},
             "resources": {
                 "aws_instance.coreos.0": {
                     "type": "aws_instance",

You can also see this by doing:

• run terraform apply. The root outputs will be printed.
• run terraform show. Outputs are printed again.
• run terraform plan. No changes are planned.
• run terraform show. The outputs are gone.
• run terraform apply. No changes.
• run terraform show. The outputs are back.

[pearkes]

Just a note that I've encountered this too.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.