Skip to content

Additional Lifecycle ignore required for metadata run.googleapis.com/operation-id #17

@mark-aops

Description

@mark-aops

When running a new plan after initial deployment of Cloud Run, we always get prompted that there is a change due to the annotation: run.googleapis.com/operation-id

Example:

 # module.cloud_run_service["run-service"].google_cloud_run_service.default will be updated in-place
  ~ resource "google_cloud_run_service" "default" {
        id                         = "locations/europe-east1/namespaces/cloud/services/run-service"
        name                       = "run-service"
        # (4 unchanged attributes hidden)

      ~ metadata {
          ~ annotations      = {
              - "run.googleapis.com/operation-id"   = "6abe3bd3-f6e7-4f00-95bb-970c63a34a84" -> null
                # (6 unchanged elements hidden)
            }
            # (6 unchanged attributes hidden)
        }

        # (2 unchanged blocks hidden)
    }

Ideally run.googleapis.com/operation-id would be added to the lifecycle ignore_changes block.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions