-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Fix Atlas tests in evergreen #1817
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Use secrets manager to initialize atlas connect variables. Change namespace in atlas and add data (user is read only). JAVA-5961
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PREPARE_SHELL is required to be able to consume the secrets from the vault.
slient: true ensures there is no output of the urls.
Looks good! Just a question - do we move the Atlas Search test data to the always-running cluster mainly to improve test speed, or for stability reasons?
@vbabanin the dev cluster was removed (not 100% on the reasoning). So a new qa cluster was added (qa should be more reliable than a dev cluster). The cluster user we use has read only, access. As the test was also read only (after setup) it made sense to add the add the data directly to the cluster. It also has the benefit of already being indexed.
Use secrets manager to initialize atlas connect variables. Change namespace in atlas and add data (user is read only).
JAVA-5961