You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2023. It is now read-only.
MongoDB Atlas uses their own labels for cloud provider regions. Here's the list of Google Cloud regions with their labels. This introduces a small amount of friction for us because if a user wants to change regions while maintaining locality they must look up both the Google Cloud region name and the corresponding Atlas region name.
We might want to try to find a way to ease this friction, perhaps by allowing the user to specify either the atlas or gcp region name and then translating it to the other.
There's an API endpoint called returnAllCloudProviderRegions but it doesn't appear to return both the atlas and provider names.
There's a lot of approaches that could work but all of them involve a level of complexity that we're not ready to commit to. Opening this issue as a place to explore ideas and discuss.
The text was updated successfully, but these errors were encountered:
MongoDB Atlas uses their own labels for cloud provider regions. Here's the list of Google Cloud regions with their labels. This introduces a small amount of friction for us because if a user wants to change regions while maintaining locality they must look up both the Google Cloud region name and the corresponding Atlas region name.
We might want to try to find a way to ease this friction, perhaps by allowing the user to specify either the atlas or gcp region name and then translating it to the other.
There's an API endpoint called
returnAllCloudProviderRegions
but it doesn't appear to return both the atlas and provider names.There's a lot of approaches that could work but all of them involve a level of complexity that we're not ready to commit to. Opening this issue as a place to explore ideas and discuss.
The text was updated successfully, but these errors were encountered: