Decommission host feature for TUI and CLI #26
Merged
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 interactive account decommissioning feature with selective SSH key retention to both TUI and CLI. Users can now safely remove accounts while choosing which SSH keys to keep on the remote host.
Motivation
When decommissioning an account, users often want to revoke Keymaster's access (remove the system key) while preserving certain user keys for continued access. Previously, decommissioning was an all-or-nothing operation that either removed the entire authorized_keys file or everything Keymaster managed. This enhancement provides fine-grained control over which keys remain on the host during decommissioning, making it safer and more flexible to transition accounts away from Keymaster management.
Changes
GenerateSelectiveKeysContentto support generating content without system keyauthorized_keysfiles end with newline (prevents terminal formatting issues)extractNonKeymasterContentto correctly identify and preserve non-Keymaster keysTesting
--keep-fileflag (CLI)Additional Notes
You can decommission in style now 😎
Fixes #17