-
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_uptime_check_config resource is always identified "change" wrongly #10884
google_monitoring_uptime_check_config resource is always identified "change" wrongly #10884
Comments
👍🏽 |
We are with the same problem in our project, this have be fixed |
Hello all, any update on this? We can use a Thanks! |
Sorry for the delay on this issue. Would you mind sharing the debug log? |
Could you try adding |
Hi shuyama1, sorry my delay. Ubaldo Brea actual config
actual terraform code
terraform plan output
|
Hi @Ubaldo-Brea! Thanks for the information provided. Looks like the API is adding a Hi All! Does anyone still see some other errors other than the |
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. |
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.Terraform Version
Terraform v1.1.2
on linux_amd64
Affected Resource(s)
google_monitoring_uptime_check_config
Terraform Configuration Files
https://github.com/liuchenggang2014/uptime_check/blob/main/single/https_uptimecheck.tf
Copy-paste your Terraform configurations here.
For large Terraform configs, please use a service like Dropbox and share a link to the ZIP file.
For security, you can also encrypt the files using our GPG public key:
https://www.hashicorp.com/security
If reproducing the bug involves modifying the config file (e.g., apply a config,
change a value, apply the config again, see the bug), then please include both:
* the version of the config before the change, and
* the version of the config after the change.
The text was updated successfully, but these errors were encountered: