Skip to content

run.googleapis.com/operation-id always triggers updates #1173

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

Closed
juliodiez opened this issue Feb 24, 2023 · 3 comments · Fixed by #1269
Closed

run.googleapis.com/operation-id always triggers updates #1173

juliodiez opened this issue Feb 24, 2023 · 3 comments · Fixed by #1269

Comments

@juliodiez
Copy link
Collaborator

juliodiez commented Feb 24, 2023

This metadata annotation in a Cloud Run service always triggers an update-in-place. Investigate what is this for and consider to avoid this behavior in the provider resource, or our module.

@rosmo
Copy link
Collaborator

rosmo commented Mar 17, 2023

Can you put an example here?

@juliodiez
Copy link
Collaborator Author

juliodiez commented Mar 17, 2023

After deploying and without doing any change in configuration, another invocation of terraform plan (excerpt):

$ tf plan
Terraform will perform the following actions:
  # module.cloud_run.google_cloud_run_service.service will be updated in-place
  ~ resource "google_cloud_run_service" "service" {
        # (4 unchanged attributes hidden)
      ~ metadata {
          ~ annotations      = {
              - "run.googleapis.com/operation-id"   = "c8ab8803-9055-46fa-9c23-6da2185400b4" -> null

Plan: 0 to add, 1 to change, 0 to destroy.
$

@juliocc
Copy link
Collaborator

juliocc commented Mar 21, 2023

This example suggests the solution is adding a lifecycle block to the google_cloud_run_service resource.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants