deployments/local-ollama-standalone.toml fails to load: bot_user is required #1274

Closed
opened 2026-10-27 13:39:43 +00:00 by sam · 0 comments
Owner

Found while adding the intake validations (b734db89). Loader.File on deployments/local-ollama-standalone.toml fails with "configuration: invalid input: bot_user is required (or define identities)" - the profile sets no bot_user and defines no identities. AGENTS.md Deployment Model lists it among the supported profiles, so a documented deployment path cannot start at all.

Pre-existing and unrelated to the intake change (verified before that edit), and reported rather than fixed because no lane owned the file.

Fix direction: either set bot_user in the profile, or make the requirement satisfiable without one. Add the regression guard the intake lane suggests: extend TestShippedProfilesValidate (internal/infrastructure/configuration) to load EVERY file in deployments/ through the production Loader, not just the two forge profiles - it already proves the technique, and it would have caught this.

Close reason

Shipped in d5763a4e: deployments/local-ollama-standalone.toml now sets bot_user = archie (line 11) with a comment explaining that standalone still needs a bot identity for chat/memory attribution. The regression guard the bead asked for is in: TestShippedProfilesValidate now globs deployments/*.toml and loads each through the production Loader (New(nil).File) then Validate, instead of naming two files. Red-first: the enumerated test failed on local-ollama-standalone.toml before the fix. dev.toml is excluded because it is a development overlay layered over an installed config (-config-overlay) rather than a standalone profile, and the exclusion map is itself checked so a renamed overlay is noticed rather than silently widening the rule. The enumeration also proved the technique: it found no further broken template beyond the one the bead named.


Imported from beads archie-core-cx0d · GitHub #1119 · type bug · priority P2 · created 2026-09-21 · closed 2026-10-02

Found while adding the intake validations (b734db89). Loader.File on deployments/local-ollama-standalone.toml fails with "configuration: invalid input: bot_user is required (or define [[identities]])" - the profile sets no bot_user and defines no [[identities]]. AGENTS.md Deployment Model lists it among the supported profiles, so a documented deployment path cannot start at all. Pre-existing and unrelated to the intake change (verified before that edit), and reported rather than fixed because no lane owned the file. Fix direction: either set bot_user in the profile, or make the requirement satisfiable without one. Add the regression guard the intake lane suggests: extend TestShippedProfilesValidate (internal/infrastructure/configuration) to load EVERY file in deployments/ through the production Loader, not just the two forge profiles - it already proves the technique, and it would have caught this. ### Close reason Shipped in d5763a4e: deployments/local-ollama-standalone.toml now sets bot_user = archie (line 11) with a comment explaining that standalone still needs a bot identity for chat/memory attribution. The regression guard the bead asked for is in: TestShippedProfilesValidate now globs deployments/*.toml and loads each through the production Loader (New(nil).File) then Validate, instead of naming two files. Red-first: the enumerated test failed on local-ollama-standalone.toml before the fix. dev.toml is excluded because it is a development overlay layered over an installed config (-config-overlay) rather than a standalone profile, and the exclusion map is itself checked so a renamed overlay is noticed rather than silently widening the rule. The enumeration also proved the technique: it found no further broken template beyond the one the bead named. --- _Imported from beads `archie-core-cx0d` · GitHub #1119 · type bug · priority P2 · created 2026-09-21 · closed 2026-10-02_
sam added the mediumbug labels 2026-10-27 13:39:43 +00:00
sam self-assigned this 2026-10-27 13:39:43 +00:00
sam closed this issue 2026-10-27 13:39:43 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1274