Andrew Gaul

Jetty 12 upgrade

6

Jetty 11 reached end of community support earlier this year: https://jetty.org/download.html. Unfortunately Jetty 12 requires Java 17 so this may cause some user pain.

Experiment with fake-gcs-server

1

References #711.

Add GCS storage backend that uses the Google SDK

2

Similar to Azure in https://github.com/gaul/s3proxy/issues/606 and Nio.2 in https://github.com/gaul/s3proxy/issues/697, using the GCS SDK instead of jclouds might allow better GCS compatibility. Given Apache jclouds will soon move to the attic...

Add a S3 storage backend that uses the AWS SDK

4

Similar to Azure in #606 and Nio.2 in #697, using the AWS SDK instead of jclouds might allow better S3 compatibility. Given Apache jclouds will soon move to the attic...

Allow reloading config via SIGHUP

1

Suggested by @arminfelder.

Use fake-gcs-server for CI

1

Similar to #700, using [fake-gcs-server](https://github.com/fsouza/fake-gcs-server) would allow better testing of GCS.

Currently these run as one task but could split to scope failures and increase test parallelism/reduce runtime.

AWS recently added support for this: https://aws.amazon.com/about-aws/whats-new/2024/11/amazon-s3-functionality-conditional-writes/ Azure already supported a similar feature: https://learn.microsoft.com/en-us/azure/storage/blobs/concurrency-manage As does GCS: https://cloud.google.com/storage/docs/request-preconditions#precondition_criteria This will require jclouds support in PutOptions.

References #313.

Consider limiting CI runners to 20

2

GitHub only gives us [20 free CI runners](https://docs.github.com/en/actions/reference/limits#job-concurrency-limits-for-github-hosted-runners) and we will have 21 (and 1 macOS) in #2738. So we should think about removing one, e.g., Fedora 41, to reduce...