Remove the legacy scp -pr host-keys/ fallback in sync_remote_host_keys(). All actively deployed lxc-* hosts now have clan vars. Targets without a clan var now get a clear error and instructions to generate one. Also extend the uncommitted-changes check to cover vars/per-machine/.
Remove the legacy `scp -pr host-keys/` fallback in sync_remote_host_keys(). All actively deployed lxc-* hosts now have clan vars. Targets without a clan var now get a clear error and instructions to generate one. Also extend the uncommitted-changes check to cover vars/per-machine/.
All actively deployed lxc-* hosts now have clan vars. Remove the legacy
scp -pr host-keys/ fallback in sync_remote_host_keys(): instead of
silently copying the gitignored directory, error clearly if no clan var
exists for the target and tell the operator how to generate one.
Also extend the uncommitted-changes check to cover vars/per-machine/ in
addition to .sops.yaml and secrets/, since clan vars must be committed
before the remote build git-pulls them.
Update the script header and sync_remote_host_keys comment to reflect
the new clan-only key flow.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B2EJ4qTsM5KUqhS5c3GAwx
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Remove the legacy
scp -pr host-keys/fallback in sync_remote_host_keys(). All actively deployed lxc-* hosts now have clan vars. Targets without a clan var now get a clear error and instructions to generate one. Also extend the uncommitted-changes check to cover vars/per-machine/.