From f29c8161bc05a4993df219735d5391c97b354e9c Mon Sep 17 00:00:00 2001 From: vincent Date: Mon, 24 Aug 2026 10:49:04 -0400 Subject: [PATCH] tigris: document shadow write-through preservation on update 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. --- tigris/index.html.markerb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tigris/index.html.markerb b/tigris/index.html.markerb index 164c831546..002b0119c6 100644 --- a/tigris/index.html.markerb +++ b/tigris/index.html.markerb @@ -199,7 +199,7 @@ flyctl storage update mybucket --shadow-name source-bucket --shadow-access-key 1 flyctl storage update mybucket --clear-shadow ``` -`--shadow-write-through` enables zero-downtime cutover by replicating every new write back to the source bucket. +When setting or changing a shadow configuration, supply all five required attributes again. On update, omit `--shadow-write-through` to preserve its current setting; pass `--shadow-write-through` to enable it or `--shadow-write-through=false` to disable it. Write-through enables zero-downtime cutover by replicating every new write back to the source bucket. ## Pricing and Billing