s3gw
s3gw copied to clipboard
s3gw-tech
Container able to run on a Kubernetes cluster, providing S3-compatible endpoints to applications.
We have a top-level Dockerfile now, but also tools/build/Dockerfile.build-radosgw and tools/build/Dockerfile.s3gw. We should look at removing the latter two and updating the docs to only refer to the top-level Dockerfile.
Add more unit tests for UI. **Note: requires said edge cases to be defined as acceptance criteria. Right now this is far too vague.**
When accessing the s3gw on localhost via the address `http://localhost:7480` while it has DNS-style bucket access enabled may end up with errorneous authentication failures. This is due to RGW interpreting...
`versioned_object` need to calculate and store the checksum.
### What needs to be done Store metadata (e.g object id, mp id, commit time, owner) with the MP part / object version file in the SFS dir tree. ###...
### What needs to be done The `s3gw-ui` backend will need to present both the UI (at `/`), as well as the API (at `/api/`) with SSL support. ### Why...
Tracks the various tasks (and Epics) related to UI Testing. This can be considered an Epic of Epics. ### Tasks - [ ] #292 - [ ] #609 - [...
### What needs to be done Develop a backend for the UI. It can be implemented using either Python or NodeJS. The UI will speak to this backend via REST...
With https://github.com/aquarist-labs/s3gw-ui/pull/269 as a quick fix to https://github.com/aquarist-labs/s3gw/issues/737 , we are essentially disabling SSL certificate validation between the UI backend and the s3gw service. This is less than ideal, because...
**To Reproduce** Steps to reproduce the behavior: ``` helm install s3gw -n s3gw --create-namespace s3gw/s3gw --set publicDomain=127.0.0.1.omg.howdoi.website --set ui.publicDomain=127.0.0.1.omg.howdoi.website --version 0.16.0 --wait helm upgrade s3gw -n s3gw s3gw/s3gw --version 0.17.0...
