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.
At the moment, in order for s3-proxy to use dashboards, they must be loaded onto s3. This is often inconvenient and sometimes users can access them.
Describe the solution you'd like
I propose to move the dashboards inside the container with the s3-proxy and enable what the user needs using the feature flags.
The text was updated successfully, but these errors were encountered:
S3-Proxy isn't created to be a static server so I'm not in favor of this solution.
What do you think of having this in a NGinX container ? This NGinX container can be deployed and another ingress can be setup on the same domain but on another path for S3-Proxy.
This will more aligned with the current form of S3-Proxy.
Is your feature request related to a problem? Please describe.
At the moment, in order for s3-proxy to use dashboards, they must be loaded onto s3. This is often inconvenient and sometimes users can access them.
Describe the solution you'd like
I propose to move the dashboards inside the container with the s3-proxy and enable what the user needs using the feature flags.
The text was updated successfully, but these errors were encountered: