2 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
rootandClaude Sonnet 5	6522a35115	Don't refuse recreating the canonical already-deployed target itself ... The duplicate-host check in create-proxmox-resource.sh compared by hostName only, so it fired even when the target being created was exactly the one variables.nix's deployedTargets already names (e.g. rebuilding lxc-nix-cache after destroying its old container to pick up new sops secrets) -- there's no other machine at risk of an identity collision in that case, just the normal redeploy workflow. Skip the check when dt == flake_target; the later VMID-existence check still guards against clobbering a resource that's actually live on the node. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-20 09:49:31 +00:00
rootandClaude Sonnet 5	00bb9b53ac	Track nix-cache's real deployment as lxc-nix-cache, not proxmox-nix-cache ... The old proxmox-nix-cache VM was destroyed and nix-cache is being redeployed as an LXC container going forward. Without this update, create-proxmox-resource.sh's duplicate-host check (which only reads this static list, not live Proxmox state) kept refusing to create lxc-nix-cache even though nothing named nix-cache actually exists on the node anymore. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-20 09:40:03 +00:00