Repository navigation
docs: fix removed and renamed cli flags in agent docs - #559
Draft
claude[bot] wants to merge 1 commit into
Draft
claude[bot] wants to merge 1 commit into
claude[bot] wants to merge 1 commit into
Conversation
Assisted-by: Claude Code Claude-Session: https://claude.ai/code/session_015Qg5NUvpUUpqnqd6ow5Xdv
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Requested by Xe Iaso · Slack thread
Before: Three of the AI agent pages showed CLI commands that no longer work. The bucket configuration page used
set-ttlandset-transition, which have been removed from the CLI, and its expiration example used a date that has already passed. The CORS and shadow bucket examples used flag names the CLI doesn't accept (--origin,--source-bucketand similar). The R2 comparison page passed--shadow-source-*flags totigris mk, which has never had them. An agent copying any of these would get an error.After: Every example uses commands and flags that exist in the current CLI. Expiration and tier transitions use
tigris buckets lifecycle create(pluslistandedit), with a future date. Shadow bucket setup usestigris buckets set-migrationwith all five required flags. The R2 migration creates the bucket withtigris mkand then sets R2 as the source withset-migration.last_reviewedis set to 2026-10-07 on the three pages.How: flags were checked against
packages/cli/src/specs.yamland the command implementations ontigrisdata/storagemain.set-ttl(L1235) andset-transition(L1331) are replaced withlifecycle create/list/edit(L1335-L1440).set-migrationnow uses--bucket,--endpoint,--region,--access-keyand--secret-key, whichlib/buckets/set-migration.tsrequires unless--disableis passed, plus the optional--write-through(L1263-L1303). This applies tobucket-configuration.md,migrate-from-any-s3-provider.mdandtigris-vs-cloudflare-r2.md.set-corsnow uses--origins,--methodsand--headerswith comma-separated values (L1500-L1535).tigris mkhas no shadow flags (L446-L520).🤖 Generated with Claude Code
https://claude.ai/code/session_015Qg5NUvpUUpqnqd6ow5Xdv
Generated by Claude Code