Provision isolated Cloud namespaces for SDK tests - #3032
Open
THardy98 wants to merge 7 commits into
Open
Conversation
THardy98
force-pushed
the
feat/cloud-test-namespace
branch
from
August 24, 2026 20:01
13ccb9b to
80d1c35
Compare
THardy98
force-pushed
the
feat/cloud-test-namespace
branch
from
August 25, 2026 12:06
80d1c35 to
e951a65
Compare
THardy98
force-pushed
the
feat/cloud-test-namespace
branch
from
August 25, 2026 17:00
e951a65 to
21ae1f4
Compare
THardy98
marked this pull request as ready for review
September 2, 2026 15:22
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 was changed?
Cloud CI now creates an isolated Temporal Cloud namespace for each workflow run and attempt. A small test-only Java command uses the SDK's existing Cloud Operations client to create an mTLS namespace, wait for provisioning, and delete it by its current resource version after tests finish.
The Cloud job passes the generated namespace and client certificate to the envconfig-backed harness. It publishes the namespace before waiting for provisioning so cleanup can still run after a partial failure, and namespace deletion runs under
always()whenever creation returned a namespace. Cleanup failures fail the job so leaked resources remain visible.This PR is stacked on #2998 and should be retargeted to
mainafter that harness PR merges.Why?
The SDK test suite needs an isolated Cloud target before it can safely expand beyond a smoke test. Per-run namespaces prevent concurrent CI runs from sharing workflow state and provide an explicit cleanup boundary without relying on long-lived namespace credentials.
Breaking changes?
None. The namespace command and Gradle tasks are internal test infrastructure.
Server PR
None.
How was this tested?
CloudTestNamespaceManagerTesttests covering namespace specifications, deletion resource versions, operation states, polling delays, and required operation IDs.temporal-sdktest task with bounded local workers.actionlint .github/workflows/ci.yml../gradlew spotlessApplyandgit diff --check.The draft PR's Cloud job provides the end-to-end create, envconfig smoke-test, and delete validation.
Operational notes
TEMPORAL_CLIENT_CLOUD_API_KEYmust have account-level permission to create, inspect, and delete namespaces inaws-ca-central-1. Workflow tests authenticate to the ephemeral namespace with the generated mTLS certificate rather than that API key.