Closed hemantxpatel closed 10 months ago
Thanks for your contribution :fire: We will take a look asap :rocket:
This issue is stale because it has been open for 14 days with no activity.
This issue was closed because it has been inactive for 7 days since being marked as stale.
This issue was closed because it has been inactive for 7 days since being marked as stale.
Feature Request
Connector currently has env
EDC_BLOBSTORE_ENDPOINT_TEMPLATE
with default valuehttps://%s.blob.core.windows.net
where placeholder%s
get replaced during runtime with azure account name.Currently Azure storage has a single domain (unlike S3), so it works. But in future, if supports multiple domain, then transfer from one domain to another will not work.
Which Areas Would Be Affected?
Let's say we want to test a Azure to Azure transfer between two participant. Each participant deploys there own Azurite locally. It will have different domains, such as
alice-azurite:10000
andbob-azurite:10000
. Hence it doesn't work which forces us to use to share a single azurite deployment for both participants.Why Is the Feature Desired?
Solution Proposal
Just Like Technology-Aws,
Technology-Azure
should also support endpoint_override option in transfer_process API.