tigris: document shadow write-through preservation on update - #2470
Draft
tripledoublev wants to merge 2 commits into
Draft
tripledoublev wants to merge 2 commits into
tripledoublev wants to merge 2 commits into
Conversation
Delete guidance advertised a nonexistent --force flag and had the empty/non-empty deletion rule backwards. fly storage destroy has no --force; it prompts for confirmation unless --yes is passed, and deletion is unconditional regardless of bucket contents. Shadow bucket create/update examples were missing the required --shadow-name flag. flyctl rejects a partial shadow configuration (all five of name, access key, secret key, endpoint, region are required) before any provider call, so the old examples would fail as written.
Clarifies that omitting --shadow-write-through on an update preserves the bucket's current setting rather than resetting it. DRAFT: depends on an in-progress flyctl fix that has not shipped yet. Do not merge until the corresponding CLI change is released.
tripledoublev
changed the base branch from
main
to
vincent/fix-tigris-shadow-delete-docs
August 24, 2026 16:23
Contributor
|
Heads up: the docs move to Mintlify next Wednesday, so this file becomes |
Base automatically changed from
vincent/fix-tigris-shadow-delete-docs
to
main
September 18, 2026 16:03
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Clarifies that omitting
--shadow-write-throughonfly storage updatepreserves the bucket's current write-through setting, rather than resetting it to disabled.Blocked — do not merge yet
This describes behavior from superfly/flyctl#5119, which has not merged. Today, omitting
--shadow-write-throughon an update still resets it to disabled. Do not merge this PR until #5119 is merged and released — otherwise this page will describe behavior that doesn't exist yet.Opened as draft, and as a separate PR from #2469, specifically so the accurate-for-today edits there aren't held up by this one.
Scope note
This branch is stacked on #2469's commit, based on
main— so the diff currently shows both PRs' changes together. It'll collapse to just this one sentence once #2469 merges; until then, treat #2469 as the source of truth for the other wording and rebase here if it changes.