Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow for configuring multiple locations per provider #36

Open
1 task done
roeap opened this issue Jan 28, 2024 · 0 comments
Open
1 task done

Allow for configuring multiple locations per provider #36

roeap opened this issue Jan 28, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@roeap
Copy link
Collaborator

roeap commented Jan 28, 2024

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 into
  • s3://bucket
  • gs://bucket

Code of Conduct

  • I agree to follow this project's Code of Conduct
@roeap roeap added the enhancement New feature or request label Jan 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant