ds seed
Defined in cli/commands/seed.ts. Deploys with the team's shared Seed token, SEED_TOKEN, read from the agent credentials file (~/.config/devstride/agent.env, which ds secrets pull writes). Needs no AWS login and no stage bind.
ds seed deploy#
ds seed deploy --stage <stage> --commit <sha> [--force] [--org <org>] [--app <app>]
Asks Seed to deploy one commit to one stage: the same request Seed's own seed deploy command sends. Merging is what deploys normally (a merge into develop deploys the dev stage, into master production), so this is only for a deliberate redeploy of a chosen commit.
| Flag | Description |
|---|---|
--stage <stage> |
The Seed stage to deploy to |
--commit <sha> |
The commit to deploy |
--force |
Deploy even when Seed finds no changes |
--org <org>, --app <app> |
The Seed organisation and app. Default: devstride for both |
It can deploy production
The token is shared and has full access (owner decision, 2026-10-05), and the command guards no stage:
--stage proddeploys that commit to production at once, without a release's review, CI or the owner's approval. Never run it againstprodwithout the owner's explicit yes.
Until the owner has created the token and stored it (pbpaste | ds secrets set agent SEED_TOKEN, then ds secrets pull on each machine), the command refuses and says how.