I am using terraform 0.14 beta, and when I run terraform plan -detailed-exitcode
, I get this output every time, even after I have run terraform apply
to save these changes:
Terraform will perform the following actions:
Plan: 0 to add, 0 to change, 0 to destroy.
Changes to Outputs:
+ cs_global_deny_arn = "arn:aws:iam::012345678901:policy/cs-global-deny-services"
+ cw_role_name = []
+ global_admin_id = "ARO2ABDCE4BDFA3D90BFC"
+ global_deny_arn = "arn:aws:iam::012345678901:policy/global-deny"
+ host_role_name = "basic-host-role"
+ policy_arn = "arn:aws:iam::012345678901:policy/global-allow-all"
+ private_app_subnet_ids = [
+ "subnet-01234560",
+ "subnet-01234561",
]
+ private_elb_subnet_ids = [
+ "subnet-01234562",
+ "subnet-01234563",
]
+ public_elb_subnet_ids = [
+ "subnet-01234564",
+ "subnet-01234565",
]
+ remediation_lambda_role_id = "ARO2C62E29C583357B2EF"
+ role_name = "cs-dashboard-cross-account-role"
+ security_group_id_ssh = "sg-01234567"
+ security_group_id_windows_base = "sg-01234568"
+ sns_topic_arn = "arn:aws:sns:us-east-1:012345678901:cloudwatch_sns"
+ unique_id = "AROBE773CCAEAED9DBDE1"
+ user_arn = "arn:aws:iam::012345678901:user/dev-jenkins"
+ user_id = "AID86DAAA6CB8DE70D89B"
+ user_name = "dev-jenkins"
+ vpc_id = "vpc-01234567"
------------------------------------------------------------------------
This plan was saved to: ./plan
This is a pain, because we use the ‘-detailed-exitcode’ option to skip the terraform apply
option if terraform plan
exits with error code 0. Because of the above, terraform plan
always exits with error code 2, requiring us to apply changes when there are none (“Plan: 0 to add, 0 to change, 0 to destroy”). None of the outputs above are outputs of the actual terraform code we’re deploying; they all come from submodules which have always only been outputted when their value changed.