feat(fleet): add opt-in SSH bootstrap and peer suggestions - #132
Merged
Conversation
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.
Easy SSH setup required ChatMux to be installed beforehand and offered no tailnet PC picker. Owners can now select a suggested SSH target and explicitly opt into first installation of a missing Linux x86_64 peer. The installation toggle defaults off.
Bootstrap downloads the canonical installer for the hub's exact stable version, fixes the backend port at 3001, and refuses existing/broken installations. It rechecks absence and atomically claims the managed root before executing the installer. Authentication files are removed before the long operation; failure or timeout does not retry or uninstall remote data. The existing host-key, restricted-key, role, capacity, and pairing checks remain in the enrollment path.
Candidate suggestions use the bounded local Tailscale status probe, expose at most 128 sanitized unique addresses only to the owner, and return
Cache-Control: no-store. Shared browser/server contracts validate these fields. CLI lifecycle diagnostics go to stderr so pairing-token stdout stays machine-readable. Network errors clear credentials and produce a closed UI error. Fleet RFC revision 6, installation/recovery guides, the roadmap, and all ten locales document the resulting behavior.Validation:
npm run verifycompleted with exit 0: audit, client/server type checks, Rust checks/tests, 2,375 repository tests, lint, identity gate, and production build.python3 scripts/cua/ssh-bootstrap-ui.py --base-url http://127.0.0.1:4341after starting Vite on port 4341. Evidence and scope are indocs/evidence/ssh-bootstrap/.Screenshots show the production form in the isolated, clearly marked fixture: