Add envconfig support to test harness - #2998
Open
THardy98 wants to merge 6 commits into
Open
Conversation
THardy98
force-pushed
the
feat/envconfig-harness
branch
from
August 11, 2026 16:59
edd4c65 to
53769e5
Compare
THardy98
marked this pull request as ready for review
August 25, 2026 16:28
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?
The internal SDK test harness can now opt into standard Temporal client environment configuration with
TEMPORAL_TEST_ENV_CONFIG_SERVER. When enabled, the existing harness loadsClientConfigProfileand uses its server address, namespace, API key, TLS settings, and gRPC metadata.Envconfig mode connects to an externally managed server and skips the harness namespace-registration step. Existing in-memory, managed dev-server, virtual-thread, and legacy
USE_EXTERNAL_SERVICEbehavior remains unchanged.CONTRIBUTING.mddocuments the developer workflow.Why?
SDK developers need to run the Java test suite against arbitrary Temporal deployments, including Temporal Cloud, without maintaining a parallel set of harness-specific client settings. Reusing envconfig lets the same TOML profiles and standard
TEMPORAL_*variables work locally and in CI.Breaking changes?
None. Envconfig mode is explicitly opt-in.
Server PR
None.
How was this tested?
ExternalServiceTestConfiguratorTestcoverage for both harness builders and required profile fields.temporal-testingandtemporal-sdktest tasks.SignalTest.signalCompletedWorkflowagainst the managed dev server.Documentation
CONTRIBUTING.mddocuments direct environment variables and TOML/profile-based configuration for the harness.