swarm: an agent's backend secrets get a store leaf of their own, and its backend environment reads back
The credentials of an agent's backend (ANTHROPIC_API_KEY and the like) move to their own leaf, swarm/agents/<agent>/backend-secrets, written through new PUT, GET and DELETE routes on /api/hives/{hive}/agents/{agent}/backend-secrets. GET says only whether any are stored. The backend environment at backend-env now reads back as stored through GET on its route, so it holds configuration only.
The agent's hive-agent-backend-env unit now runs on every agent with a store, reads both leaves and writes the configuration and then the secrets into the one file the harness and the subagent daemon load, so a secret wins over a variable of the same name. It removes the file when the store holds neither. The harness counts an agent whose environment holds ANTHROPIC_API_KEY or ANTHROPIC_AUTH_TOKEN as API-billed, so it tries the key instead of waiting for a Claude login; a real 401 still sets needs-login. The controller's policy may delete the new leaf.
Tests: the secret-client path, the controller routes, the script test of the unit with a stub bao, the module-eval cases and the harness's mode check. Docs: the swarm UI routes, the credentials reference and the API-key provider page.
This commit is contained in:
parent
c9204ad0e0
commit
33fdd5205e
1 changed files with 737 additions and 107 deletions
|
|
@ -454,14 +454,19 @@ in
|
|||
//
|
||||
lib.optionalAttrs
|
||||
(
|
||||
(config.services.hyperhive.agent.runtime == "acp" || config.services.hyperhive.agent.useApiKey)
|
||||
(
|
||||
config.services.hyperhive.agent.runtime == "acp"
|
||||
|| config.services.hyperhive.agent.useApiKey
|
||||
|| config.services.hyperhive.agent.bao.addr != null
|
||||
)
|
||||
&& config.services.hyperhive.agent.backendEnvironment.environmentFiles != [ ]
|
||||
)
|
||||
{
|
||||
# A subagent authenticates with the same credentials as the
|
||||
# harness: an ACP subagent to its provider, a claude subagent of
|
||||
# an api-key agent with `ANTHROPIC_API_KEY`, as it has no OAuth
|
||||
# session to fall back on.
|
||||
# session to fall back on. An agent with a store may have a key
|
||||
# an operator stored there, which the fetched file carries.
|
||||
EnvironmentFile = config.services.hyperhive.agent.backendEnvironment.environmentFiles;
|
||||
};
|
||||
};
|
||||
|
|
|
|||
Loading…
Reference in a new issue