Repository navigation
Conversation
…dead device cleanup
This was referenced Oct 25, 2026
Owner
Author
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.
Stacked on #332.
Why
The tailnet has 54 devices (2 online): duplicates (
himachal/himachal-1,kerala/kerala-1), six deadgate-*/repro-*test VMs, andinventory.ymlpointing at stale addresses (himachal100.73.3.51). Root cause of the-1names: the tailscale role's pre-join cleanup used the OAuth client secret as a classic API key; Tailscale answers 401,failed_when: falsehid it, and nothing was ever deleted. The secret in Bitwarden (tailscale-apikey) is itself rejected by Tailscale today (token exchange returns 401), so a new OAuth client is needed.What
scripts/tailnet.pyaudit / gc / rename / fix-inventory / sync / release; dry run unless--apply; reads fall back to localtailscale status.just tailnet-audit,just tailnet-sync,just seed-tailnet-oauth(verifies the secret before writing to Bitwarden).tailnet.py release.docs/src/tailnet.md;inventory_parsergainsparse_host_vars/set_host_var(comment-preserving).--k8s-daysis passed.Verified
Local dry run against the live tailnet plans: delete 2 duplicates + 6 test VMs, rename himachal-1 and kerala-1, fix himachal's IP, drop kerala's override. Applying needs the new OAuth client (not done). Unit tests cover the planner and inventory edits.