Skip to content

WKBCH-24: Add S3 lifecycle expiration support#76

Merged
dvasilas merged 2 commits intomainfrom
improvement/WKBCH-24-lifecycle-expiration
Apr 17, 2026
Merged

WKBCH-24: Add S3 lifecycle expiration support#76
dvasilas merged 2 commits intomainfrom
improvement/WKBCH-24-lifecycle-expiration

Conversation

@dvasilas
Copy link
Copy Markdown
Contributor

Add S3 lifecycle expiration as a new workbench feature and fix container data cleanup requiring sudo.

Changes

  • Add features.lifecycle.enabled flag, starts backbeat lifecycle conductor, bucket-processor, and object-processor
  • Vault setup creates lifecycle IAM user and role, injects credentials into backbeat config.
  • Replace host bind mounts with named Docker volumes for container data directories — root-owned files were making workbench destroy fail without sudo

Host bind mounts under ./data/ are created by containers running as
root, making them undeletable without sudo. Named volumes are managed
by Docker and cleaned up by docker compose down --volumes, which
the destroy command already uses.
Vault setup creates a lifecycle IAM user with AssumeRole
permissions, creates the lifecycle-role in the internal services
account (accountSeeds only cover user-created accounts), and
injects the generated credentials into the backbeat config.
@dvasilas dvasilas merged commit e8067e5 into main Apr 17, 2026
2 checks passed
@dvasilas dvasilas deleted the improvement/WKBCH-24-lifecycle-expiration branch April 17, 2026 15:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants