Skip to content

Removed defaultMongoDBVersion api call in builders. MongoDB version i… #4054

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

Merged
merged 2 commits into from
Jul 24, 2025

Conversation

jeroenvervaeke
Copy link
Collaborator

@jeroenvervaeke jeroenvervaeke commented Jul 24, 2025

Proposed changes

  • Got rid of api call in the internal/cli/clusters/create.go builder.
  • Had to introduce usage.MDBVersionCreate, because I didn't want the update commands to be affected by the docs change.

Made every single api call command 100% faster 🚀

Jira ticket: CLOUDP-333404

@jeroenvervaeke jeroenvervaeke requested review from a team as code owners July 24, 2025 10:11
@github-actions github-actions bot added need-doc-review Improvements or additions to documentation, will be reviewed by the docs team atlascli labels Jul 24, 2025
Copy link
Contributor

APIx Bot :bowtie:: a message has been sent to Docs Slack channel 🚀.

@fmenezes
Copy link
Collaborator

@jeroenvervaeke did you test this against prod? I vaguely remember we had to add a number instead of blank because our tests / prod / dev all behave differently.

@jeroenvervaeke
Copy link
Collaborator Author

@jeroenvervaeke did you test this against prod? I vaguely remember we had to add a number instead of blank because our tests / prod / dev all behave differently.

I've tested against QA.
Sending a blank is not working indeed, but null should work (it's a *string, not string, hence my update).

According to the prod api docs:

MongoDB major version of the cluster. Set to the binary major version.

On creation: Choose from the available versions of MongoDB, or leave unspecified for the current recommended default in the MongoDB Cloud platform. The recommended version is a recent Long Term Support version. The default is not guaranteed to be the most recently released version throughout the entire release cycle. For versions available in a specific project, see the linked documentation or use the API endpoint for project LTS versions endpoint.

@jeroenvervaeke
Copy link
Collaborator Author

Ran the e2e tests that were failing on evergreen. Everything looks green.

@jeroenvervaeke
Copy link
Collaborator Author

Note to future self: This PR could cause an issue when releasing MongoDB 9.0, but this problem should be resolved by merging #4050

fmenezes
fmenezes previously approved these changes Jul 24, 2025
Copy link
Collaborator

@fmenezes fmenezes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉 thanks for the offline discussion

@fmenezes
Copy link
Collaborator

if you want you can update the snaphots by adding update-snaphots label, I think we will need to do it on master at least

@github-actions github-actions bot removed the need-doc-review Improvements or additions to documentation, will be reviewed by the docs team label Jul 24, 2025
@jeroenvervaeke jeroenvervaeke enabled auto-merge (squash) July 24, 2025 15:43
Copy link
Contributor

Coverage Report 📈

Branch Commit Coverage
master 2b6741c 25.7%
CLOUDP-333404 3e171a3 25.7%
Difference 0%

@jeroenvervaeke jeroenvervaeke merged commit 77e367e into master Jul 24, 2025
22 checks passed
@jeroenvervaeke jeroenvervaeke deleted the CLOUDP-333404 branch July 24, 2025 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants