storage-canary: prove allowed-prefix list access (TIN-1546) - #433
Merged
Conversation
Jesssullivan
force-pushed
the
codex/tin-1546-storage-list-gate
branch
from
May 21, 2026 05:20
d3f613e to
045df4f
Compare
Jesssullivan
had a problem deploying
to
tcfs-storage-prod-smoke
May 21, 2026 05:20 — with
GitHub Actions
Failure
Jesssullivan
temporarily deployed
to
tcfs-storage-prod-smoke
May 21, 2026 05:22 — with
GitHub Actions
Inactive
Jesssullivan
force-pushed
the
codex/tin-1546-storage-list-gate
branch
2 times, most recently
from
May 21, 2026 05:27
c501397 to
d4226c9
Compare
Jesssullivan
temporarily deployed
to
tcfs-storage-prod-smoke
May 21, 2026 05:28 — with
GitHub Actions
Inactive
Jesssullivan
force-pushed
the
codex/tin-1546-storage-list-gate
branch
from
May 21, 2026 05:32
d4226c9 to
79dbad4
Compare
Jesssullivan
force-pushed
the
codex/tin-1546-storage-list-gate
branch
from
May 21, 2026 05:38
79dbad4 to
671ee9c
Compare
Jesssullivan
marked this pull request as ready for review
May 21, 2026 06:15
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
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
tcfs storage canary --jsonexercise the same allowed-prefixlist()permission used by daemon health and index enumerationlist_prefix,list_ms,list_count, andlistedin the canary reportremote_prefixso production reruns can stay inside the scopedgha/storage-posture/...allow policyWhy
The production storage posture canary passed write/read/delete and deny-scope proof, but the Linux public package smoke failed because it used
gha/linux-postinstall/..., outside thetcfs-storage-prod-smokecredential allow scope. The tightened canary now proves allowed-prefix list access, and package smoke workflows can be dispatched against a prefix that matches the production credential scope instead of widening the S3 policy or misclassifying package failures.Evidence
Validation
~/.cargo/bin/cargo fmt --all -- --check~/.cargo/bin/cargo test -p tcfs-cli storage_canarybash scripts/test-linux-postinstall-workflow.shbash scripts/test-release-workflow-fileprovider.shbash scripts/test-tcfs-alpha-gate-preflight.shbash -n scripts/tcfs-alpha-gate-preflight.sh scripts/test-tcfs-alpha-gate-preflight.sh scripts/test-linux-postinstall-workflow.sh scripts/test-release-workflow-fileprovider.shgit diff --checkBoundaries
This is branch evidence until PR #433 lands. After merge, rerun the same Linux smoke from
mainor the next release candidate using a prefix undergha/storage-posture/.... The macOS production FileProvider rename proof still needs a fresh package built after current-main rename-manifest preservation.