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
Is your feature request related to a problem? Please describe.
The current setup assumes that there is either a single bucket per provider, or at least that all locations share the same credential.
We should allow for configuring dedicated locations, possibly assigning a default credential that is used, when no dedicated credential for that provider is available.
Describe the solution you'd like.
Define some sort of registry, that takes the form of the well know URLs, including the host.
az://container <-- requires additional account into
s3://bucket
gs://bucket
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Contact Details
No response
Is your feature request related to a problem? Please describe.
The current setup assumes that there is either a single bucket per provider, or at least that all locations share the same credential.
We should allow for configuring dedicated locations, possibly assigning a default credential that is used, when no dedicated credential for that provider is available.
Describe the solution you'd like.
Define some sort of registry, that takes the form of the well know URLs, including the host.
az://container
<-- requires additional account intos3://bucket
gs://bucket
Code of Conduct
The text was updated successfully, but these errors were encountered: