-
Notifications
You must be signed in to change notification settings - Fork 529
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 to configure subpaths within S3 buckets #2100
Comments
I'd like to take this issue up! |
Hi, @shrey is there any update on this issue? |
Hi, I would like to pick this up since there no reply from assigned user. Let me know if I can work on this. One question,
|
@kousikmitra We would love to have you give this a shot. Thanks for taking an interest!
It would be cool if we made it to all 3 backends at once. However, we appreciate any contribution and if s3 is all you can carve out some time to for, we understand.
Yes, this change should be entirely doable in |
@mapno I would love to make the change for other backends. If thats ok I will create another ticket and work on it. |
Please, go ahead. Thanks for contributing to Tempo! |
@mapno I have raised a PR with all changes. Can you please reopen the issue and update the description? |
Done! |
Is your feature request related to a problem? Please describe.
Tempo's S3 config does not support using specific folder within an S3/GCS/Azure bucket to use as its root folder. This doesn't allow cleanly sharing buckets with other apps.
Describe the solution you'd like
Tempo should add support for subpaths within S3/GCS/Azure buckets.
Describe alternatives you've considered
Bucket names with
/
are not allowed per S3's bucket naming rules.Additional context
Similar issues in Mimir grafana/mimir#1682 and Loki grafana/loki#5889
The text was updated successfully, but these errors were encountered: