Skip to content
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

chore: Supports legacy API in create when using old schema with num_shards #2892

Merged
merged 2 commits into from
Dec 14, 2024

Conversation

EspenAlbert
Copy link
Collaborator

Description

Supports legacy API in create when using old schema with num_shards

Link to any related issue(s): CLOUDP-287995

Type of change:

  • Bug fix (non-breaking change which fixes an issue). Please, add the "bug" label to the PR.
  • New feature (non-breaking change which adds functionality). Please, add the "enhancement" label to the PR. A migration guide must be created or updated if the new feature will go in a major version.
  • Breaking change (fix or feature that would cause existing functionality to not work as expected). Please, add the "breaking change" label to the PR. A migration guide must be created or updated.
  • This change requires a documentation update
  • Documentation fix/enhancement

Required Checklist:

  • I have signed the MongoDB CLA
  • I have read the contributing guides
  • I have checked that this change does not generate any credentials and that they are NOT accidentally logged anywhere.
  • I have added tests that prove my fix is effective or that my feature works per HashiCorp requirements
  • I have added any necessary documentation (if appropriate)
  • I have run make fmt and formatted my code
  • If changes include deprecations or removals I have added appropriate changelog entries.
  • If changes include removal or addition of 3rd party GitHub actions, I updated our internal document. Reach out to the APIx Integration slack channel to get access to the internal document.

Further comments

Copy link
Member

@lantoli lantoli left a comment

Choose a reason for hiding this comment

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

nice!

@@ -190,7 +191,12 @@ func (r *rs) createCluster(ctx context.Context, plan *TFModel, diags *diag.Diagn
if pauseAfter {
latestReq.Paused = nil
}
_, _, err = api.CreateCluster(ctx, projectID, latestReq).Execute()
if usingLegacySchema(ctx, plan.ReplicationSpecs, diags) {
Copy link
Member

Choose a reason for hiding this comment

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

can we add an acc test that would fail before this change?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

See comment here: https://github.com/mongodb/terraform-provider-mongodbatlas/pull/2892/files#r1885034045
I don't know if we have any test that would have a failure by using this old API as I'm not 100% sure that it triggers ISS or auto_scaling_mode=SHARD 🤔

@@ -90,7 +90,7 @@ steps:
text: "true"
- path: /api/atlas/v2/groups/{groupId}/clusters
method: POST
version: '2024-10-23'
version: '2024-08-05'
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@lantoli you can see the required update here

Copy link
Member

Choose a reason for hiding this comment

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

@EspenAlbert oh, nice!

@EspenAlbert EspenAlbert marked this pull request as ready for review December 14, 2024 12:03
@EspenAlbert EspenAlbert requested a review from a team as a code owner December 14, 2024 12:03
@EspenAlbert EspenAlbert merged commit b59c241 into master Dec 14, 2024
45 checks passed
@EspenAlbert EspenAlbert deleted the CLOUDP-287995_create_two_api_versions branch December 14, 2024 12:03
lantoli added a commit that referenced this pull request Dec 14, 2024
* master:
  chore: Supports legacy API in create when using old schema with num_shards (#2892)
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