Joao Eduardo Luis
Joao Eduardo Luis
### What needs to be done Longhorn-specific support should be dropped. We should instead rely on the user to specify a PVC of their choosing. ### Why it needs to...
### What needs to be done By dropping Longhorn requirements, we will need to update our docs to reflect that. ### Why it needs to be done Longhorn is no...
- [ ] Make sqlite_modern_cpp the primary dbconn / connection pool abstraction - [ ] retry utilty support
### What needs to be done The dashboard at https://status.s3gw.tech should get an updated look and feel, following our current branding. Some things also need to be updated from the...
In a k8s context, it is expected that if a given service secret is updated, then it will be reflected in said service's application. This is, apparently, the behavior of...
 As shown in the image above, building a Release Candidate resets the `latest` tag to point to the RC. This is potentially problematic if the RC is not yet...
During the release workflow, we must run the UI's end to end tests as a validation step. This will ensure the `s3gw-ui` container about to be released does not contain...
Currently, we are building the final object synchronously, during the `complete` request. This works fine because we rely on `copy_file_range()` to perform the data copy -- thus avoiding reading and...
Instead of exposing the user of `s3gw` to `RGW_.*` prefixed environment variables to set the seed access and secret keys, use `S3GW_.*` environment variables instead. This can potentially be achieved...
What the title says. Although this is far too vague. Requires said edge cases to be defined as acceptance criteria for this issue.