Provision Cloud namespace for each test run - #541
Merged
Conversation
THardy98
force-pushed
the
feat/cloud-namespace-per-run
branch
from
August 17, 2026 18:01
47594bb to
34fb2c6
Compare
THardy98
force-pushed
the
feat/cloud-namespace-per-run
branch
from
August 17, 2026 19:55
c6bb7ba to
9c8f276
Compare
THardy98
force-pushed
the
feat/cloud-namespace-per-run
branch
from
August 18, 2026 02:13
9c8f276 to
05a1ac5
Compare
THardy98
marked this pull request as ready for review
August 18, 2026 02:28
chris-olszewski
requested changes
Aug 18, 2026
chris-olszewski
left a comment
chris-olszewski
left a comment
Member
There was a problem hiding this comment.
Can the cloud_namespace.rb script get moved to temporalio/extra? That's where we keep all of our scripting logic and linting etc is already setup for it.
chris-olszewski
approved these changes
Aug 18, 2026
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.
What was changed
Cloud CI now generates a short-lived certificate authority and client certificate, provisions an ephemeral Temporal Cloud namespace that trusts that authority, and runs the existing envconfig-backed workflow smoke test against it. Namespace cleanup runs after the test even when provisioning or execution fails, and cleanup failures are reported as warnings.
This PR is stacked on #534 and follows the namespace lifecycle established by the Python and .NET SDKs.
Why?
This isolates parallel Cloud CI runs instead of sharing a persistent namespace and serializing access to it.
Checklist
Closes N/A
How was this tested:
actionlint .github/workflows/ci.ymlAny docs updates needed?
No. This is internal test and CI infrastructure.