Provision isolated Cloud namespaces for SDK tests - #3032
Draft
THardy98 wants to merge 1 commit into
Draft
Conversation
THardy98
force-pushed
the
feat/cloud-test-namespace
branch
from
August 24, 2026 20:01
13ccb9b to
80d1c35
Compare
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 test-only Java command uses the SDK's Cloud Operations client to create the namespace with a generated mTLS certificate authority, wait for the asynchronous operation, and delete it by its current resource version after the tests finish.
The Cloud job runs the existing workflow smoke test through the envconfig-backed harness using the generated client certificate. The Cloud Operations client check targets the same namespace using the account API key. Namespace cleanup runs after test or provisioning failures when creation returned a namespace; cleanup failures are reported as warnings with the namespace name.
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 single smoke test. Per-run namespaces prevent concurrent CI runs from sharing workflow state and provide an explicit cleanup boundary without relying on long-lived client credentials.
Breaking changes?
None. The namespace command and Gradle tasks are internal test infrastructure.
Server PR
None.
How was this tested?
./gradlew :temporal-sdk:test --tests 'io.temporal.client.CloudTestNamespaceManagerTest'(7 tests passed)./gradlew :temporal-sdk:tasks --allactionlint .github/workflows/ci.yml./gradlew spotlessApplygit diff --checkThe full local
temporal-sdkrun completed 1,705 tests successfully and reproduced one unrelated failure inAsyncPollerTest#testSuspendPolling; CI will provide the clean-environment regression result.Operational notes
TEMPORAL_CLIENT_CLOUD_API_KEYmust have account-level permission to create, inspect, and delete namespaces inaws-ca-central-1. The workflow tests authenticate to the ephemeral namespace with the generated mTLS certificate rather than that API key.