Skip to content

Conversation

rozza
Copy link
Member

@rozza rozza commented Oct 6, 2025

Use secrets manager to initialize atlas connect variables. Change namespace in atlas and add data (user is read only).

JAVA-5961

Use secrets manager to initialize atlas connect variables.
Change namespace in atlas and add data (user is read only).

JAVA-5961
@rozza rozza requested a review from vbabanin October 6, 2025 09:37
@rozza rozza requested a review from a team as a code owner October 6, 2025 09:37
@rozza
Copy link
Member Author

rozza commented Oct 6, 2025

silent: true
working_dir: "src"
script: |
# DO NOT ECHO WITH XTRACE (which PREPARE_SHELL does)
Copy link
Member Author

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.

@vbabanin
Copy link
Member

vbabanin commented Oct 16, 2025

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 vbabanin mentioned this pull request Oct 16, 2025
@rozza
Copy link
Member Author

rozza commented Oct 16, 2025

@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.

@rozza rozza merged commit e1bf5f5 into mongodb:main Oct 16, 2025
46 of 55 checks passed
@rozza rozza deleted the JAVA-5961 branch October 16, 2025 10:08
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