-
Notifications
You must be signed in to change notification settings - Fork 189
Can't create cluster ME_SOUTH_1 region #157
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
Comments
Hi @kostyazgara Just went through source code and documentation, and its a limitation in MongoDB Atlas API. Availability limited to the following regions: US_EAST_1 https://docs.atlas.mongodb.com/reference/api/clusters-create-one/ Terraform Provider is using go-mongodbatlas-client. |
@xmariopereira Thank you for an answer. So, it means there no options to add supporting other regions? If I send As you can see, all works. And mu cluster was created in me-south-1 region I suppose this issue in go-mongodbatlas-client? Who can help me to add this option? Because I don't know Go language and create PR will take to much time for me :) |
Sorry, I didn't read correctly the documentation. M140 is not available in that Regions. Sorry!!! Still checking the code it shouldn't error out.
|
Okay, if it not available, why I can still create a cluster in that region via curl request? Or I'm something missed? |
@kostyazgara I have one of our developers looking into this (@PacoDw). @xmariopereira thank you so much for providing help here too! |
fyi @shum for 👁 while I'm OOO^ |
Hi! If you have another comment or concern, just let us know 👍 |
@PacoDw Thanks for the fast reaction! I really appreciate your work. Could you say me, when approximately the PR would be merged and I can use an updated provider in the terraform? P.S. Can I close an issue? |
Ahhh the regions here hardcoded in the provider.go. Glad I could help! |
Thank you so much! |
Hi again! I see you released a new version 0.4.1 of MongoDB atlas terraform plugin that should fix the issue with the creation cluster in other regions. But seems it still doesn't work correctly. Here my logs:
What can be wrong? I have tried to make |
Edit - I don't think this fix made it in 0.4.1 and will be in our next release. I'm going to test with the master branch @kostyazgara I tested ME_SOUTH_1 creation and it failed for me as well - however creating it directly via the API did work so it seems the provider is still not working correctly for this region. I apologize for that. @PacoDw and @marinsalinas the fix in 0.4.1 does not seem to work. |
@themantissa this is not in the new release, just in master branch. |
@PacoDw I realized that right after I posted my reply, apologizes. @kostyazgara the fix for this will be in 0.4.2 but I will test it to be sure in the current master branch. |
@kostyazgara 0.4.2 is out. You should be good now! |
I am trying to create M10 cluster in AWS me-south-1 region but got an error.
Here my request payload in trace mode

And the response from them

My terraform file


And plan
Also, I have tried to create cluster in us-east-1 region and them was successful

Seems to terraform provider erase my

regionName
when I setME_SOUTH_1
but why? In documentation mentioned that Mongo Atlas supports me-south-1 regionCan you help me?
Thanks in advance!
The text was updated successfully, but these errors were encountered: