HARMONY-2168: Make sure the environment variable ENVIRONMENT does not override the harmony environment#118
Merged
Merged
Conversation
… override the harmony environment used in client configuration.
ygliuvt
approved these changes
Aug 25, 2025
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
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.
Jira Issue ID
HARMONY-2168
Fixes #116
Description
When constructing a Harmony Client the ENVIRONMENT env var was incorrectly overriding the desired harmony environment. This PR changes the code to ignore the ENVIRONMENT env var so that the behavior is to use the environment passed into the client constructor or default to production if no environment is passed in.
Local Test Steps
This should fail on the main branch but pass in this branch.
You can test other combinations like
harmony_client = Client(should_validate_auth=False, env=Environment.UAT)as well.PR Acceptance Checklist