Skip to content

Conversation

THardy98
Copy link
Contributor

@THardy98 THardy98 commented Jul 28, 2025

What was changed

The profile parameter is now optional, instead of defaulting to a value of default.

Why?

A defined profile value is an explicit request for a specific profile in a provided configuration. Providing a default value made it impossible for a user to provide zero configuration (they would have to define a default profile in their TOML).

However, we want to allow users to provide zero configuration and have it default to localhost:7233 address and default namespace.

This change makes that possible in combination with temporalio/sdk-core#968

  1. How was this tested:
    Existing integration tests

  2. Any docs updates needed?
    This change achieves parity with the docs

@THardy98 THardy98 requested a review from a team as a code owner July 28, 2025 21:23
@THardy98 THardy98 changed the title Env config - make profile optional Env config - make profile optional Jul 28, 2025
@THardy98 THardy98 marked this pull request as draft July 28, 2025 21:24
@THardy98
Copy link
Contributor Author

Marking as draft until temporalio/sdk-core#968 is merged (will update core submodule after). This gives us default values for address and namespace

@THardy98
Copy link
Contributor Author

THardy98 commented Aug 4, 2025

Marking as draft until temporalio/sdk-core#968 is merged (will update core submodule after). This gives us default values for address and namespace

No longer blocked (core PR closed).

@THardy98 THardy98 merged commit 1573433 into main Aug 4, 2025
26 of 28 checks passed
@THardy98 THardy98 deleted the fix_env_config_profile_fallback branch August 4, 2025 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants