archetypes: create an agent from an archetype with no config repo
POST /api/agents takes an archetype the stored list holds, records it in the new agent-archetype bucket, and queues no CreateRepo, AddRepoMember or InitAgentConfigRepo for it. A destroy clears the key. Hives may read the bucket. Refs #5386
This commit is contained in:
parent
6b93839290
commit
b199c83899
7 changed files with 645 additions and 37 deletions
|
|
@ -59,6 +59,9 @@ agent-limits = ["async-nats/jetstream"]
|
|||
# `Permission` names, so the crates that only need the bucket name do not link
|
||||
# it.
|
||||
agent-permissions = ["dep:hive-sh4re", "async-nats/jetstream"]
|
||||
# `agent_archetype::read`, for hive-c0re, which reads the archetype of each
|
||||
# agent it provisions or rebuilds. Explicit for the same reason as `notices`.
|
||||
agent-archetype = ["async-nats/jetstream"]
|
||||
|
||||
[dependencies]
|
||||
# Bare (no `kv`/`jetstream`) unless a consumer opts into the `kv` feature
|
||||
|
|
|
|||
Loading…
Reference in a new issue