G1c: point nexus deploy-flake defaults + rotation steps at allod/deploy #15
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
allod/nexus!15
Loading…
Reference in a new issue
No description provided.
Delete branch "agent/nexus-deploy-flake-defaults"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of the archetypes/profiles repo split —
Refs allod/strategy#18. This is the G1c pre-cliff re-point.The framework repo was renamed
allod/profiles→allod/archetypes(M0), and the deploy composition root isallod/deploy. Nexus provisioning still defaulted its deploy flake and rotation lock-bump steps to~/work/allod/profiles, which resolves only through the dying rename redirect. This PR moves every redirect-sensitive default and operator-facing lock-bump step onto theallod/deploycheckout before the redirect dies when the newallod/profilesdefinitions repo is created (M1). The existing deploy template already re-exportsnixosConfigurationsandvmFacts, so these re-points are valid pre-split.Changes:
DEPLOY_FLAKEdefault inprovision-vm-from-host/rebuild-vm-from-host:$HOME/work/allod/profiles→$HOME/work/allod/deploy. Matching updates to thenexus.provisioning.deployFlakeoption example/description,docs/provisioning-scripts.md, the/template/profiles→/template/deploysentinel inflake.nix(fixture +host-provisioning-envassertion), and thevm-provisioning-test-plan.mdsmoke-test line.forge-ssh-key,vm-ssh-host-key,nexus-host-key): the checkout default now resolvesdeploy(allod/deployfallback), the variable is renamedMACHINE_PROFILES/PROFILES_CHECKOUT→DEPLOY_CHECKOUT, the printed "update the deploy flake" steps andforge-ssh-key'sassert_cleanguard the deploy checkout.rotate-token: the "Update the deploy flake lock" steps andnixos-rebuild --flake ~/work/allod/deploy#…lines move to the deploy checkout.verify-vm-from-host: dropped the deadMACHINE_PROFILESassignment (assigned, never read) rather than repointing it.bootstrap-vm-from-host.sh: unchanged — its optional${MACHINE_PROFILES}/scripts/hooks/<vm>.shlookup is a profiles-definitions concern and keeps resolving the definitions checkout (resolve_checkout profiles … allod/profiles), per plan.Remaining
allod/profilesreferences in nexus (reviewed, all intentional / non-redirect-sensitive):scripts/bootstrap-vm-from-host.sh:9— the optional profile-hook lookup (kept by design).tests/bootstrap-orchestration.sh(bootstrap hook tests),tests/registry-resolver.sh(resolver unit data),tests/provisioning-contract.sh(health-check sample repos),tests/forge-ssh-key.sh:178(dead fixture registry entry). None resolves through the redirect; these belong to the M5 broad grep sweep.Risk
R2 Medium — mechanical but provisioning-adjacent (it governs which flake cold provisioning/rotation builds and bumps). Rollback before M1 is a straight revert; the redirect still serves until then. The three per-VM lock-bump scripts' tests override the checkout var and assert on printed text, so
nix flake checkalone cannot prove they were repointed — hence the direct greps below.Validation
allod-agent referenced this pull request2026-08-24 14:20:55 +01:00