SERVICE_UNAVAILABLE error is no longer expected in cloud-dev and QA when migrating sharded and geo-sharded clusters from old schema to new. This behavior is not expected in prod at this point and will be tracked separately, hence no other changes required in code/docs right now.
Link to any related issue(s):
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.
[ ] 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.
Description
SERVICE_UNAVAILABLEerror is no longer expected in cloud-dev and QA when migrating sharded and geo-sharded clusters from old schema to new. This behavior is not expected in prod at this point and will be tracked separately, hence no other changes required in code/docs right now.Link to any related issue(s):
Type of change:
Required Checklist:
Further comments
Test run: https://github.com/mongodb/terraform-provider-mongodbatlas/actions/runs/11935742861/job/33267774284