docs: rollback workflow guide + abac access-control catalog drift#210
Open
coryodaniel wants to merge 1 commit into
Open
docs: rollback workflow guide + abac access-control catalog drift#210coryodaniel wants to merge 1 commit into
coryodaniel wants to merge 1 commit into
Conversation
…v:decommission, rollback callout) User prompts: - "update the abac guide and the docs ../docs with rollback and any other permissions that are missing" - "in the docs pr, also include a workflow on rollbacks equal quality to the other workflow guides" Changes: - docs/workflows/04-rollback.md: new guide. Modeled on 01-fork-environment.md / 02-promote.md / 03-preview-environments.md — what rollbackDeployment does, snapshot semantics, why approval pins the package release pointer (vs. proposeDeployment for one-shot behavior), authorization (instance:propose + instance:deploy), GraphQL flow, what does/doesn't get snapshotted (md_metadata refreshed; secrets stay with the instance), explicit "not the right tool" callouts (older version pin, schema down-migrations, out-of-band resources). - docs/workflows/00-overview.md: add rollback bullet to the section index. - docs/platform-operations/security/02-access-control.md: add environment:deploy + environment:decommission to the Environment permissions table (catalog had them, doc didn't); call out rollback proposals under instance:propose; tighten environment:delete description (empty env required); update SRE common-pattern example to include instance:propose + env-level deploy/decommission so the rollback workflow's "oncall authors and approves" pattern composes. The permission count line is left alone — adding the two env actions brings the existing "39 permissions" count into actual sync with the catalog as visible on this page. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Member
Author
|
@claude please review the rollback workflow guide for parity with the existing fork / promote / preview guides, and verify the access-control catalog additions against |
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
1 participant
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
Two related additions:
New workflow guide: `/workflows/rollback` — modeled on the depth and shape of the existing fork / promote / preview guides. Covers what `rollbackDeployment` actually does (snapshot semantics, what gets carried forward vs. refreshed), the approval flow, why approval pins the package release pointer, authorization (`instance:propose` to author, `instance:deploy` to approve), and the cases where rollback is the wrong tool (down-migrations, secret reverts, one-shot deploys).
Access-Control page drift fix — same content the in-repo `docs/guides/abac.md` got in massdriver#3284:
Files
Test plan
Out of scope (deliberate)
🤖 Generated with Claude Code