Document the site hosting credential contract in the integration doc #45
No reviewers
Labels
No labels
blocked
bug
decision
duplicate
enhancement
help wanted
invalid
landed?
question
ready-to-merge
stale
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!45
Loading…
Reference in a new issue
No description provided.
Delete branch "agent/site-credential-contract-doc"
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?
Documentation only; nothing changes for a running machine. The integration doc gains a "Site hosting credential" section that tells a fork where
allod site deploy's credential comes from: the file rclone reports as its configuration, which on the host is~/.config/rclone/rclone.conf, placed there by the framework fromnexusIdentity.siteHostingConfigFile(allod/secrets#17, allod/archetypes#74), with the human forge token placed the same way fromnexusIdentity.userForgejoTokenFile. It gives the lifecycle in one place: create once withallod site config, move the stanza into the deployment's secrets repository, rotate throughrotate-tokenonce allod/nexus#42 lands and by re-encrypting until then, verify withallod site check. The wrapper comment innix/home.nixgains two lines pointing at that contract; no code in that file changes. The flake still evaluates, and every command and path named was checked against the tools source. If anything here is wrong it is a doc edit, not a rollback. Merge after allod/archetypes#74 so the doc describes something that exists.Closes allod/nexus#44. Refs allod/strategy#51.
Risk
R0. Prose and a comment.
Validation
nix flake showandnix eval .#homeModules.host --apply builtins.typeOfsucceed after the comment edit.allod sitesubcommand named (deploy,check,config,config show,config update,config replace) exists incmd/allod/site.gousage text; the symlink refusal for all three writing actions and the config-path resolution throughrclone config filewith theRCLONE_CONFIG/XDG_CONFIG_HOMEfallback were read incmd/allod/site_config.go; neither variable is set by the nexus or archetypes host modules.git diff master --stat:docs/integration.mdandnix/home.nixonly.configcreate also refusing a symlink) were verified against source and applied, the third (the rotate-token format not existing yet, which the doc states) was rejected; both reviewers report no findings on the final diff.Labels are unavailable to this token; none is warranted.