lifecycle: drop manager port special case (#753) — manager hashes into 8100..8999 like every other agent
This commit is contained in:
parent
f9a492f7a9
commit
4526e40a49
11 changed files with 43 additions and 39 deletions
|
|
@ -20,10 +20,13 @@
|
|||
//!
|
||||
//! Ports come from [`crate::lifecycle::agent_web_port`] — pure
|
||||
//! FNV-1a(name) hash so the value is reproducible from the name
|
||||
//! alone. The manager is intentionally excluded: it sits at the
|
||||
//! fixed `MANAGER_PORT` (8000) and the gateway routes `/` straight
|
||||
//! to it without a per-agent prefix (see `nix/modules/hive-gateway.nix`
|
||||
//! upstream config, atlas's #740).
|
||||
//! alone. The manager is intentionally excluded from the map: the
|
||||
//! gateway routes `/` straight to it via the c0re dashboard upstream
|
||||
//! (see `nix/modules/hive-gateway.nix`, atlas's #740) rather than a
|
||||
//! per-agent `/agent/<name>/` prefix. Post-#753 the manager's port
|
||||
//! is computed by the same hash as every other agent, but it still
|
||||
//! doesn't appear here — keeping the routing surface "sub-agents
|
||||
//! only" matches the gateway's current shape.
|
||||
//!
|
||||
//! Atomicity: write to a sibling `.tmp` file + rename so a partial
|
||||
//! write never leaves an unparseable file in place. The gateway's
|
||||
|
|
|
|||
Loading…
Reference in a new issue