Chris LuandGitHub 813f1351f8 feat(s3/lifecycle): enable scheduler by default (#9492) ...

S3 lifecycle is a standard bucket feature — operators set
PutBucketLifecycleConfiguration through the S3 API expecting the
configured expirations to actually fire. With the prior default
(scheduler enabled=false), buckets with lifecycle XML silently
retained data past their declared expiration until an operator
noticed and turned the scheduler on.

The failure mode of enabled-by-default is "worker runs every day
and fast-exits on buckets with no lifecycle rules" — cheap.
The failure mode of disabled-by-default is "data lingers, looks
like it expired, doesn't" — bad. Enabled-by-default matches both
the AWS S3 default behavior and the operator's natural mental
model.

Operators who want the worker off can still disable it via the
admin UI; once a persisted config exists, this descriptor default
no longer applies (the persisted Enabled state wins).

Test pins the choice so a future flip to false fails loud.

2026-05-13 16:57:10 -07:00

..

tasks

feat(s3/lifecycle): enable scheduler by default (#9492)

2026-05-13 16:57:10 -07:00

types

fix(ec): skip re-encode when EC shards already exist for the volume (#9448) (#9458)

2026-05-11 23:12:57 -07:00

client.go

fix(mini): shut down admin/s3/webdav/filer before volume/master on Ctrl+C (#9112)

2026-04-16 16:11:01 -07:00

log_adapter.go

Admin UI: Fetch task logs (#7114)

2025-08-09 21:47:29 -07:00

registry.go

chore: remove ~50k lines of unreachable dead code (#8913)

2026-04-03 16:04:27 -07:00

worker.go

fix(mini): shut down admin/s3/webdav/filer before volume/master on Ctrl+C (#9112)

2026-04-16 16:11:01 -07:00