Skip to content

feat(s3)!: support explicit bucket layouts - #4913

Open
shepilov wants to merge 1 commit into
masterfrom
feat/s3-precreated-buckets
Open

feat(s3)!: support explicit bucket layouts#4913
shepilov wants to merge 1 commit into
masterfrom
feat/s3-precreated-buckets

Conversation

@shepilov

@shepilov shepilov commented Sep 11, 2026

Copy link
Copy Markdown
Member

Summary

  • Configure default and per-type S3 destinations with bucket names and optional connection URLs together in one map.
  • Separate objects by type and instance so shared-bucket reads, listings, and deletion stay scoped.
  • Support pre-created buckets with bounded startup checks, optional automatic creation, and environment overrides.
  • Replace generated bucket names and document the configuration and object layout.

Closes #4912.

@shepilov
shepilov force-pushed the feat/s3-precreated-buckets branch from bb76d4f to 9f27863 Compare September 11, 2026 13:01
@shepilov
shepilov marked this pull request as ready for review September 11, 2026 13:03
@shepilov
shepilov force-pushed the feat/s3-precreated-buckets branch 2 times, most recently from ba0bad6 to c64157d Compare September 11, 2026 14:39
@shepilov shepilov changed the title feat(s3): support pre-created buckets and per-bucket connections feat(s3)!: support explicit bucket layouts Sep 11, 2026
Configure a default bucket and per-type bucket assignments, with optional
per-bucket connections and pre-created bucket checks.

BREAKING CHANGE: S3 storage requires explicit bucket names and uses
type-prefixed object paths. Generated bucket names are no longer supported.
@shepilov
shepilov force-pushed the feat/s3-precreated-buckets branch from c64157d to 7a8bb37 Compare September 11, 2026 15:04
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.

Allow S3 deployments to use pre-created buckets

1 participant