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

This does not work with single bucket mode / s3 at all because the bucket names are hardcoded to project name #149

Open
sharkymcdongles opened this issue Sep 6, 2023 · 5 comments
Labels
bug Something isn't working

Comments

@sharkymcdongles
Copy link

Describe the bug
analyzer always tries to upload to project name buckets and cannot be configured to upload to a single bucket at a particular path.

Expected behavior
Same behavior as the other services with bucketname respected.

@sharkymcdongles sharkymcdongles added the bug Something isn't working label Sep 6, 2023
@tomikonio
Copy link

tomikonio commented Mar 28, 2024

Hi 🙂
Is it still the case?
We would like to switch from minio to S3 eventually.
If it cannot use S3, what are the implications of the analyzer service using an ephemeral Filesystem storage?

@yoavws
Copy link

yoavws commented Apr 7, 2024

Hi we faced this issue as well.
Is there any update here? 👍

@kondratm
Copy link

kondratm commented Apr 7, 2024

Same issue here, can it be prioritized please?

@yoavws
Copy link

yoavws commented Jun 26, 2024

Is there any update on this issue? we want to migrate to a RP +S3 deployment.
also any workaround?

@tomikonio
Copy link

Hi, any updates?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants