Repository navigation
Runbooks: the check, and every alert, job and notice of spin - #2
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…cedures an operator is asked for (#1) Thirty-three runbooks grounded in spin's code: one per Grafana alert rule (some covering a pair), every control plane job named in exactly one, the four owner notices, and the procedures - host shell, quarantine, recover, the database's restore and handover, key rotation, a lost runner, a lockout, egress denials, third-party terms. What spin cannot do yet is a TODO naming its issue. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Closes #1
The repository's shape and its first content.
task check(cmd/check, the Gate workflow runsgo tool task check): front matter (id = file name, kebab case, unique; title; severity critical|warning|info; owner; last_reviewed a date;applies_toalerts/jobs/events/dashboards), the six sections in order, no raw HTML and no images (goldmark's AST, not a regexp), links to runbooks that exist and otherwise only app paths, https or mailto, and nothing a public repository must not carry (an AWS account id or access key, a private key, an installation's hostname). Plus taskgate and sfw from go-tools, pinned as brand pins them.applies_to.jobs, the four owner notices (HELD, STOP_BACKUP_FAILED, UNRESPONSIVE, REHOMED), and the procedures: host shell, quarantine, recover --accept-data-loss, database restore/handover, key rotation, lost runner, admin lockout, egress denials, third-party terms.Not run on a real installation: the log queries (
spin admin logsfield names), the psql path in admin-lockout, the self-hosted runner upgrade steps in runners-behind.🤖 Generated with Claude Code