Repository navigation
docs: add disaster recovery and emergency workspace access cutoff pages - #32356
Draft
nickvigilante wants to merge 1 commit into
Draft
nickvigilante wants to merge 1 commit into
nickvigilante wants to merge 1 commit into
Conversation
Customers ask for more than the one-paragraph disaster recovery note in the validated architecture docs. Add a disaster recovery explanation under Install > Operate and a how-to for cutting off workspace access during a security incident under Admin > Security. Refs DOCS-1214
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.
Summary
Adds a disaster recovery page and a how-to for cutting off workspace access during a security incident.
Customers keep asking for more than the one-paragraph disaster recovery note in the validated architecture docs.
Changes
docs/install/operate/disaster-recovery.md(explanation): database backups, restore testing, what HA does and doesn't cover, outage impact for direct and relayed connections, and orphaned resources after a restore.docs/admin/security/cut-off-workspace-access.md(how-to): common situations that need a cutoff and the best practice that prevents each, what each action blocks, ordered cutoff steps, then investigation and restoring access.Notes for reviewers
agent/agent.gorunLoop), so the page says the agent keeps running and reconnects, and makes no buffering claim.tailnet/configmaps.go: when the coordinator connection drops, peers are marked lost and removed only afterlostTimeout(15 minutes) with no WireGuard handshake. The page leaves the constant out.putUserStatusand the API key and agent middleware reject new requests, and I found nothing that closes existing connections. I didn't run it.coder list --allignores--search(cli/cliui/filter.go), so the stop-all command uses--search "status:running"without--all.jqexpression was checked against theowner_nameandnamefields ofcodersdk.Workspace.Testing
make lint/emdash,make lint/docs-manifest,make lint/docs-html, andmake lint/docs-redirects(offline) pass.Plan and decision log
workspace_builds.provisioner_state; built-in PostgreSQL under the config root (cli/server.go); suspension rejects API keys and agent auth (coderd/httpmw/apikey.go,coderd/httpmw/workspaceagent.go); owners and self can't be suspended (coderd/users.go);coder tokens removeacts only on the caller's tokens (cli/tokens.go); expire endpointPUT /api/v2/users/{user}/keys/{keyid}/expire;coder stopacceptsowner/name(codersdk.ResolveWorkspace); dashboard page size 25.coder delete --orphanfor those.This PR was generated by Coder Agents on behalf of @nickvigilante.