Open shaunkillingbeck opened 2 years ago
Had some issue when trying to just add an output
In this case the lines in compact_plan.py
don't match. We do have a line Changes to Outputs:
that could be used?
Output sample below:
module.network.module.public-ovo.module.zone_1.google_compute_instance_group_manager.nat: Refreshing state... [id=projects/billing-statements-aus-prod/zones/australia-southeast1-a/instanceGroupManagers/prod-aus-permanent-ovo-nat-australia-southeast1-a]
module.network.module.public-ovo.module.zone_3.google_compute_instance_group_manager.nat: Refreshing state... [id=projects/billing-statements-aus-prod/zones/australia-southeast1-c/instanceGroupManagers/prod-aus-permanent-ovo-nat-australia-southeast1-c]
Changes to Outputs:
+ container_registry = "australia-southeast1-docker.pkg.dev/billing-statements-aus-prod/default"
You can apply this plan to save these new output values to the Terraform
state, without changing any real infrastructure.
Warning: Deprecated Attribute
with module.network.module.public-ovo.google_compute_firewall.public_ovo_ingress_allow_ovo,
on ../../modules/aus/public-ovo/ovo.tf line 41, in resource "google_compute_firewall" "public_ovo_ingress_allow_ovo":
41: enable_logging = true
Deprecated in favor of log_config
(and one more similar warning elsewhere)
Releasing state lock. This may take a few moments...
There is a more recent feature that allows resources to be moved via configuration rather than
terraform state mv
commands. A very handy feature!Unfortunately, when there is only a "move" action to perform, the lines that
compact_plan.py
looks for to find a plan are not printed and so it is not treated as a plan. For example:The full output including all the
Refreshing state...
lines is added to the GitHub comment, and when this is later compared withcmp.py
it is unlikely to ever match because theRefreshing state...
lines do not appear in a deterministic order. As such CD pipeline will continue to fail and changes will not be applied.