Open Shantanu-11 opened 3 months ago
Same issue
Same issue for us,
~ event_trigger {
# (2 unchanged attributes hidden)
+ failure_policy {
+ retry = false
}
}
on every apply...
At the risk of adding a me-too comment: we are also seeing this, but with an interesting wrinkle. We have multiple GCP projects in play here, and the same terraform plan produces the spurious diffs but only in one of the projects.
as a workaround, but not ideal in some cases. You can add a lifecycle policy to prevent these to appear in your plan
lifecycle {
ignore_changes = [
source_archive_bucket,
source_archive_object,
]
}
use it careful as it ignores changes in source and object
Multiple users are experiencing the same issue, and due to all the permissions and configurations that this ticket involves I'm forwarding it directly
@ggtisc Any updates on this?
@ggtisc Any updates on this?
this should have been fixed for a while
Community Note
Terraform Version & Provider Version(s)
Terraform v1.2.7 on
Affected Resource(s)
google_cloudfunctions_function
Terraform Configuration
Debug Output
No response
Expected Behavior
No changes were detected in the terraform plan as your configuration matches the infrastructure.
Actual Behavior
There are changes detected in
source_archive_bucket
andsource_archive_object
and terraform is trying to set them to null. These values were never being set from our configuration. As for the retry being set to false in the failure_policy block, I have had this asfalse
for a long time and nothing has changed around thisUpon applying these changes the apply fails with an error.
Steps to reproduce
Create a google_cloud_function without specifying
source_archive_bucket
ORsource_archive_object
Important Factoids
This has been happening since 1st of May, 2024.
References
No response
b/340347166