the harness no longer publishes the agent's icon; the controller is its only writer
This commit is contained in:
parent
2e30163d5c
commit
fe4d68c13f
1 changed files with 15 additions and 170 deletions
|
|
@ -971,13 +971,6 @@ in
|
|||
# responder as the empty expansion of an unset `SWARM`.
|
||||
"--agent-token-publish-subject ${lib.escapeShellArg "\$\$SWARM.term.{agent}"}"
|
||||
"--agent-token-publish-subject ${lib.escapeShellArg "\$\$SWARM.agent-state.{agent}"}"
|
||||
# Its own key in the `agent-icons` KV bucket, and nothing else
|
||||
# of JetStream. A KV put is a JetStream publish to
|
||||
# `$KV.<bucket>.<key>`, acked on the client's inbox, so this
|
||||
# one subject is the whole write. The harness publishes to the
|
||||
# subject directly instead of opening the bucket, so it needs
|
||||
# no `$JS.API.*` subject; swarm-controller creates the bucket.
|
||||
"--agent-token-publish-subject ${lib.escapeShellArg "\$\$KV.agent-icons.{agent}"}"
|
||||
# Its own key in the `agents-md` KV bucket
|
||||
# (`swarm_queue_client::agents_md`), on the same terms: the
|
||||
# harness mirrors its `AGENTS.md` there for the swarm to read.
|
||||
|
|
|
|||
Loading…
Reference in a new issue