chore: align repo coordinates with the renamed infra repositories - #10
Merged
Conversation
The infra repositories were renamed so each is named after the tool that applies its contents: homelab-hosts to nix-config, homelab-deploy to fleet-infra, nix-platform to nixos-modules, and platform-blueprints to flux-modules. GitHub redirects the old URLs, but stale coordinates in flake inputs, workflow references, scripts and docs obscure which repository owns what. Every repository coordinate now uses the current name. Flake input identifiers are renamed alongside their URLs, and the corresponding flake.lock node keys and repo fields are updated so the lock stays consistent with the declaration; revision hashes are unchanged because a rename does not alter content. The PLATFORM_BLUEPRINTS_ environment variable prefix becomes FLUX_MODULES_, and scripts/lib is renamed to match. The camelCase platformBlueprints NixOS option is deliberately untouched: renaming a module option is a breaking API change and is handled separately.
ExtraToast
added
type: chore
ExtraToast
added
type: chore
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
1 participant
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.
Why
The infra repositories were renamed so each is named after the tool that applies its contents:
homelab-hoststonix-config,homelab-deploytofleet-infra,nix-platformtonixos-modules, andplatform-blueprintstoflux-modules. GitHub redirects the old URLs indefinitely, so the rename itself broke nothing — but stale coordinates in flake inputs, workflow references, scripts and docs obscure which repository owns what, which is the problem the rename set out to solve.What changed
flake.locknode keys andrepofields are updated so the lock stays consistent with the declaration. Revision hashes andnarHashvalues are unchanged, because a repository rename does not alter content.PLATFORM_BLUEPRINTS_environment variable prefix becomesFLUX_MODULES_, andscripts/lib/platform-blueprints.shis renamed toscripts/lib/flux-modules.sh.Deliberately not changed
platformBlueprintsNixOS module option. Renaming a module option is a breaking API change for every host that sets it, and it is handled on its own rather than buried in a coordinate sweep.deploy-config-schemakeeps its repository and package name. Renaming it implies an npm package rename for eight consumers, so it is paired with the planned breaking shrink instead of costing consumers two migrations.Verification
Production reconciles from a different repository entirely, so this org carries no live traffic and the coordinate sweep cannot affect a running cluster. CI on each repository is the gate.