Skip to main content

GCP Run Revision

A Cloud Run Revision is an immutable snapshot of a Cloud Run Service configuration and the container image that will be executed. Each time you deploy a new container image or change configuration settings (memory, environment variables, VPC connection, execution service account, etc.), Cloud Run automatically creates a new revision and routes traffic according to your chosen rollout strategy. Revisions make it possible to roll back quickly, perform gradual traffic splits, and audit exactly what code and configuration were active at any point in time.

Official documentation: https://cloud.google.com/run/docs/deploying#revisions

Supported Methods​

  • GET: Get a gcp-run-revision by its "locations|services|revisions"
  • LIST
  • SEARCH: Search for gcp-run-revision by its "locations|services"

Possible Links​

gcp-compute-network​

If the revision is configured to use a Serverless VPC Connector, it is implicitly attached to the underlying VPC network. This link represents the network traffic that will originate from, or be routed to, that specific gcp-compute-network.

gcp-iam-service-account​

Every revision runs with an execution identity. The service account specified in the revision’s serviceAccountName field determines the permissions the container has when it calls other GCP APIs. This link surfaces that relationship.

gcp-cloud-kms-crypto-key​

Environment variables and mounted secrets within the revision can be encrypted with a customer-managed Cloud KMS key. If such a key is referenced, the revision will be linked to the corresponding gcp-cloud-kms-crypto-key.

gcp-artifact-registry-docker-image​

The revision points to a specific container image stored in Artifact Registry or Container Registry. Linking the revision to the gcp-artifact-registry-docker-image shows exactly which image digest is being executed.

gcp-compute-subnetwork​

When a Serverless VPC Connector is used, the connector is attached to a particular sub-network. The revision therefore has an indirect dependency on that gcp-compute-subnetwork, which defines the IP range through which outbound traffic will flow.