-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
google_monitoring_dashboard: resource still has perma diffs #16173
Comments
@c2thorn here is the dedicated issue |
@c2thorn did you have time to look into this? |
We face the same issue. Would be really helpful to get this resolved! |
same issue, please fix |
still an issue in 1.7.0 and provider v5.18.0 |
Hello! This issue still persists - tf version 1.7.0, provider v.5.20.0 |
The issue is still presists. Tested in Terraform Version 1.8.2 and 5.26.0 for google terraform provider. |
Given no progress have been made on this, we switched from mosaicLayout to row layout and were able to get rid of the issues. Also removing fields that are defaults helped. This shouldn't be necessary though... |
++ this still exists |
still an issue with mosaic layout. tf 1.9.5, provider 6.0.1 |
I found a solution to the problem. I used to always get the dashboard JSON from the GCP UI, using the 'Copy JSON' option. Turns out this gets a bunch of garbage that throws terraform off. Instead, we do this now and the diffs aren't showing anymore: gcloud monitoring dashboards list --format=json | jq '.[] | select(.displayName == "YOU DASHBOARD NAME") | del(.name, .etag)' |
This fixed the problem for us too, thanks! |
What also works:
jq 'del(..|nulls)' removes all null and empty values which are causing the issues in the first place |
@cpl-alanb that's a bit difficult to achieve if you need to dynamically and conditionally construct the JSON |
Hello! Is there an official solution for this issue? |
@laura-lindberg-sap no there is none. |
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.I hope this helps reproduce the issue and I hope we don't need to wait until the next major version again to get this fixed 😅
This is a long-standing annoyance, polluting the changes when applying Terraform, leading to important differences needing to be noticed more easily.
Terraform Version
v1.6.0
Affected Resource(s)
Terraform Configuration Files
Full Example reproducing the issue:
Minimal example reproducing the issue
Terraform output after re-planning (with perma diffs):
Debug Output
Expected Behavior
Re-planning shows "No changes".
Actual Behavior
Re-planning shows changes needed for Terraform.
Steps to Reproduce
terraform apply
terraform plan
Important Factoids
It seems like using the
mosaicLayout
or some specific fields leads to this issue, but I'm not sure if that's indeed the case.References
b/304483210
The text was updated successfully, but these errors were encountered: