chore(e2e): use getters for default connections access instead of constant variables COMPASS-10308#7786
Open
gribnoysup wants to merge 1 commit intomainfrom
Open
Conversation
gribnoysup
added
the
no-title-validation
gribnoysup
changed the title
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
2 participants
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.
In the refactored Atlas Cloud tests we will be adding new connections (clusters) dynamically during the global "before" test configuration, this doens't work well with the current way we access these variables that are syncronously defined on the test run start. This patch is a small refactor to make sure that when we dynamically populate
DEFAULT_CONNECTIONS, all other places can access up to date information about those