Add a Cloud Run worker sample#325
Open
steps-re wants to merge 1 commit into
Open
Conversation
Signed-off-by: Mike German <mike@stepsventures.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
2 participants
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.
Adds a
cloud_run_worker/sample: a Temporal worker packaged to run on Google Cloud Run, mirroring the existinglambda_worker/sample.A Temporal worker is a long-running poller, not an HTTP server, but a Cloud Run service must answer its startup probe on
$PORTor it never becomes healthy. So the worker starts a tiny stdlib health endpoint (200 ok) on$PORTin a daemon thread before connecting to Temporal, and the deploy uses--no-cpu-throttlingso the background poller keeps running between requests. Includes the Dockerfile, a deploy script, a workflow + activity, and a README with a "Why a health server?" section.Verified: the image builds via Cloud Build, and running it confirms the health server binds
:8080before the Temporal connect, so the startup probe passes. A full end-to-end run needs a reachable Temporal server / Temporal Cloud namespace.