Repository navigation
docs: document vprox credential rotation - #25
Merged
Merged
Conversation
Capture the staged rotation procedure, verification gates, and recovery steps so an operator can repeat the work without relying on chat history.
|
Keep the runner rollout requirement in this service runbook and remove the dependency on a separate fa coordination runbook.
shreyas-blacksmith
approved these changes
Oct 21, 2026
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.


Add a detailed operator runbook for rotating passwords across both vprox control servers and enabled relays. It covers singular/plural password semantics, the actual deployed Doppler config, gateway coverage and management access, bind-address lifetime checks, relay session drain, client transition, retirement, and recovery.
Include separate old/new/invalid probes for the control endpoint and the relay handshake. The relay probe verifies the channel-bound server proof. The runbook is self-contained and states that runner hosts must be rolled and outgoing old-key jobs must finish before retirement; it also explains how an excluded gateway can safely return to service.
Validated Bash/Python snippets, relative links, and Go formatting on Blacksmith Testbox; the embedded relay probe compiles against this repository. No production configuration or runtime code changes.
Related service runbooks: