keep the operator list under one key and read it with one direct get
The agent read the operator-profiles bucket with a keys() listing, an ordered consumer whose grant (STREAM.INFO, CONSUMER.CREATE) and flow-control reply had never run against a permissioned queue. The controller now writes the whole list as one JSON array under one key, only when it changed, and the agent reads it with one DIRECT.GET the way agent_inference::read_own reads its key. The agent grant shrinks to that one subject.
This commit is contained in:
parent
6942f8fd27
commit
49015eb553
12 changed files with 254 additions and 201 deletions
|
|
@ -228,7 +228,7 @@ pub mod agent_limits;
|
|||
pub mod agent_permissions;
|
||||
|
||||
/// The bucket swarm-controller publishes each operator's name and forge-profile
|
||||
/// pronouns in — one key per operator, read by every agent. The names are
|
||||
/// pronouns in — one key holding the whole list, read by every agent. The names are
|
||||
/// unconditional; writing needs `kv` and reading needs `operator-profiles`.
|
||||
pub mod operator_profiles;
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue