Watch
0
0
Fork
You've already forked hyperhive
0
hyperhive/hive-meta-flake
Repository files (latest commit first)
Filename Latest commit message Latest commit date
atlas f3c0a87c0f hand agents the queue address at container start
HIVE_AGENT_NATS_URL now reaches each container in its hive facts, from
the host's deploy.hive-controller.queue.agentNatsUrl, instead of being
rendered into the meta flake. The agent option
services.hyperhive.agent.queue.natsUrl is removed; the harness unit
imports the queue credential whenever the token endpoint is set.

On deploy every agent rebuilds once (the rendered flake loses the
address), and the harness reads the address from the facts file
hive-priv writes before each start.

Refs #4857
2026-10-24 21:13:24 +02:00
..
src hand agents the queue address at container start 2026-10-24 21:13:24 +02:00
Cargo.toml move the meta flake render into the hive-meta-flake crate 2026-10-24 21:13:24 +02:00
README.md move the meta flake render into the hive-meta-flake crate 2026-10-24 21:13:24 +02:00

hive-meta-flake

The meta flake's flake.nix text: one nixosConfigurations.<agent> per agent, each built from hyperhive's agent-base plus the agent's config input or archetype.

Pure string rendering, with no IO and no environment reads. The caller passes the hyperhive pin, the agents with their pins, and the values every agent container gets. hive-c0re and swarm-controller both call render_flake, so there is one renderer.