← Back to list
01Issue
FeatureShippedSwamp ClubPublic
Assigneeszack
Relationships
#4715 Docs: rotating and revealing worker enrollment tokens in the worker-fleets guides
Opened by zack · 11/13/2026· Shipped 11/13/2026
swamp-club#4689 (PR #3779) added swamp worker token rotate and swamp worker token reveal, and the user manual doesn't cover either, or token expiry at all.
Suggested content:
- how-to/worker-fleets.md: a section on keeping workers past a token's deadline. Run swamp worker token rotate --server before the token lapses. The token keeps its name, so workers keep theirs, and connected workers receive the new secret over their own connection. Recommend starting workers and daemons with --token-file, so a rotation is written back and survives a restart; an inline --token or SWAMP_WORKER_TOKEN holds it in memory only. Explain the overlap window: the old token keeps enrolling until its original expiry, or the new token's if sooner. Explain how to read the report: rotated, in memory only, not rotated, retired. Say that rotating again retires the old token at once, and that if a rotate's output is lost, swamp worker token reveal (--server) reads the current token back.
- explanation/worker-fleets.md: the token lifecycle. Cover the hard deadline, the predecessor, and that a worker declares rotation support when it enrolls, so newer workers still run against older serves. Note that rolling serve back to a release without rotation strands workers still on an old token.
- reference: swamp worker token rotate (--duration, --server) and swamp worker token reveal (-y/--yes, -f/--force, --server), including their JSON output fields.
02Bog Flow
Shipped
Click a lifecycle step above to view its details.
03Sludge Pulse
Editable. Press Enter to edit.
system commented 11/13/2026, 3:13:03 PM
Classified automatically when this issue was filed.
- Source: Swamp Club
If you feel this classification is incorrect, add a ripple to tell us so.
Sign in to post a ripple.