Add Google Cloud Run worker identity/deployment helper - #1776
Draft
seanbollin wants to merge 1 commit into
Draft
Conversation
Adds an experimental Google Cloud Run helper, mirroring the existing AWS Lambda module's worker-ID behavior. Because Cloud Run runs a long-lived container (unlike Lambda's per-invocation model), this is a metadata helper rather than a worker wrapper: it reads the Cloud Run instance metadata -- the instance id from the metadata server, plus the worker pool/service name and revision from CLOUD_RUN_WORKER_POOL / CLOUD_RUN_REVISION (worker pools) or K_SERVICE / K_REVISION (services) -- and derives a worker identity and a WorkerDeploymentVersion to apply to a normal long-lived worker. Covers both Cloud Run worker pools and services. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
The Python SDK already ships an AWS Lambda worker module (
temporalio/contrib/aws/lambda_worker) that sets the worker "ID" for Lambda. This adds the equivalent capability for Google Cloud Run, covering both Cloud Run worker pools and services.Cloud Run runs a long-lived container, so — unlike Lambda's per-invocation handler — there is nothing to wrap. This PR adds a small metadata helper module at
temporalio/contrib/gcp/cloud_run. It's marked experimental.What it does
get_google_cloud_run_metadata(), called once at worker startup:CLOUD_RUN_WORKER_POOL(worker pools) →K_SERVICE(services), and the revision fromCLOUD_RUN_REVISION→K_REVISION, andhttp://metadata.google.internal/computeMetadata/v1/instance/id, headerMetadata-Flavor: Google) for the unique instance id (available on both worker pools and services).It returns a
GoogleCloudRunMetadataexposing ready-to-pass values:.worker_identity→<instance_id>@<revision>, forClient.connect(..., identity=...); and.worker_deployment_config→ aWorkerDeploymentConfig(version=..., use_worker_versioning=True), forWorker(..., deployment_config=...).(
.worker_deployment_versionis also exposed.)Notes
GoogleCloudRun-style, experimental marking) intentionally mirrors the coordinated Google Cloud Run effort already visible in the .NET SDK (Temporalio.Extensions.Gcp.CloudRun.OpenTelemetry).urllib.request) for the HTTP call.worker_deployment_configuses a deferred import so identity-only use doesn't pull in the worker package.ruff check,ruff format --check,pydocstyle, andmypyall clean. (A fullimport temporalio...needs the compiled Rust bridge, which isn't built in my sandbox; the module's logic was verified directly instead.)🤖 Generated with Claude Code