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
It makes using this action really much harder than needed, as for example during black friday, no new cosmosdb instances can be created in useast. The region override mechanism seems to be way to crude as you'd have to fixate a specific region while the actions runner could be in various regions. At first thought, I'd expect to always use the same region as the action runner calling this action?
The text was updated successfully, but these errors were encountered:
It has been a long while since this was introduced, so our memory is hazy.
This was to resolve an issue with Cosmos being setup in regions where it wouldn't work. This may not be a problem anymore and be removed, or perhaps the action could be refactored to use a blacklist that is configurable (this action predates config values being supported).
We don't have any plans to update this action at the moment.
What is the reason for the region restrictions defined in https://github.com/Particular/setup-cosmosdb-action/blob/config/azure-regions.config?
It makes using this action really much harder than needed, as for example during black friday, no new cosmosdb instances can be created in useast. The region override mechanism seems to be way to crude as you'd have to fixate a specific region while the actions runner could be in various regions. At first thought, I'd expect to always use the same region as the action runner calling this action?
The text was updated successfully, but these errors were encountered: