Skip to content

fix: preserve bucket configs during site adoption - #90

Merged
Vonng merged 2 commits into
mainfrom
codex/issue-78-preserve-bucket-config
Aug 29, 2026
Merged

fix: preserve bucket configs during site adoption#90
Vonng merged 2 commits into
mainfrom
codex/issue-78-preserve-bucket-config

Conversation

@Vonng

@Vonng Vonng commented Aug 29, 2026

Copy link
Copy Markdown
Member

Summary

  • preserve existing full Object Lock retention during same-name bucket adoption
  • preserve enabled custom versioning, including excluded prefixes/folders
  • bootstrap missing configs and timestamps
  • explicitly enable suspended or invalid versioning instead of silently leaving replication on a non-versioned bucket

Dependency

Stacked on the #76 Object Lock wire-field repair.

Validation

  • focused normal/race and go vet ./cmd
  • adversarial review cases for minimal/full lock documents, custom enabled versioning, suspended versioning, and invalid repair

Refs #78. CreatedAt event-order semantics remain in #77-A.

Keep existing Object Lock and enabled versioning documents and timestamps when adopting a same-name bucket. Bootstrap missing configs, enable suspended versioning, and retain custom excluded-prefix settings.

Signed-off-by: Feng Ruohang <rh@vonng.com>
@Vonng
Vonng changed the base branch from codex/issue-76-object-lock-wire to main August 29, 2026 11:39
@Vonng
Vonng merged commit 514a041 into main Aug 29, 2026
8 checks passed
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.

1 participant