Bad assumption in isCosmosEndpoint.ts makes it impossible to run azurite table service using custom ports. #32239
Labels
bug
This issue requires a change to an existing behavior in the product in order to be resolved.
Client
This issue points to a problem in the data-plane of the library.
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
needs-team-attention
Workflow: This issue needs attention from Azure service team or SDK team
Service Attention
Workflow: This issue is responsible by Azure service team.
Tables
Describe the bug
Since 13.3.0 and the introduction of the CosmoDB table support, it is impossible to start the azurite emulator on custom ports for the table service and make table access with a SAS key anymore.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Accessing the table should match the authorizations from the SAS key.
Additional context
This happens because of this line:
azure-sdk-for-js/sdk/tables/data-tables/src/utils/isCosmosEndpoint.ts
Line 14 in 83efc34
Which basically assumes that if this is not the default emulator port it must be CosmoDB...
In our local setup we have cases where we want to emulate locally our data separation in multitenant mode by accessing different azure storage servers depending on tenant. So we need to be able to run multiple azurite instances on custom ports to achieve that.
The text was updated successfully, but these errors were encountered: