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
|
|
@ -14,18 +14,12 @@
|
|||
//! container is stopped: the value's lifetime is the agent's, not its
|
||||
//! placement's.
|
||||
//!
|
||||
//! **Two writers, one value.** The swarm controller writes the key from the
|
||||
//! **The swarm controller is the only writer.** It writes the key from the
|
||||
//! builder's reply when it builds the agent for a deploy: the builder reads the
|
||||
//! icon from the agent's config, so this write needs no running agent. The
|
||||
//! agent's harness writes the same key, from the same config, with its own
|
||||
//! queue credential, which the auth callout grants `$KV.agent-icons.<agent>` and
|
||||
//! no other key. On either side an icon that is not set deletes the key.
|
||||
//!
|
||||
//! The harness publishes to [`subject`] directly instead of opening the
|
||||
//! bucket, so that one subject is its whole grant. Creating the bucket is left
|
||||
//! to the reader (`swarm_queue_client::agent_icon::open_or_create`). A write
|
||||
//! that arrives before the bucket exists is refused with "no stream", and the
|
||||
//! harness retries.
|
||||
//! icon from the agent's config, so the write needs no running agent. An icon
|
||||
//! that is not set deletes the key. No agent credential may write here, and the
|
||||
//! controller creates the bucket (`swarm_queue_client::agent_icon::open_or_create`).
|
||||
//! [`subject`] is the subject a KV put to a key goes to.
|
||||
|
||||
/// The KV bucket agent icons are published into, keyed by agent name.
|
||||
///
|
||||
|
|
|
|||
Loading…
Reference in a new issue