docs+nix: fix stale peer-hives-dashboard references (hyperhive#3294)
Follow-up to the peer-hives removal: docs/web-ui/dashboard.md drops the whole "P33R H1V3S" section + its stale #peers hash and tab-strip mentions; docs/swarm/README.md's runtime-effects list and cross-references point at swarm-ui's roster page instead. Nix comments in hive-c0re/environment.nix, swarm.nix and swarm-wireguard.nix that described HYPERHIVE_PEERS/certFingerprint as dashboard-consumed are updated to say what's actually still true (agent identity only). Deliberately NOT removed: the `certFingerprint` nix option itself. It has no remaining Rust consumer, but deleting a documented, potentially already-set option is a bigger, breaking change than removing dead display code — flagged in docs/swarm/README.md with a note instead of silently dropped, so an operator or reviewer can make that call explicitly rather than have it made for them here.
This commit is contained in:
parent
016ab70e31
commit
8c8f0e2758
5 changed files with 39 additions and 67 deletions
|
|
@ -211,10 +211,13 @@ in
|
|||
}
|
||||
// lib.optionalAttrs (config.services.hyperhive.swarm.peerHives != { }) {
|
||||
# Peer hives serialised as a JSON array of {domain, cert_fingerprint,
|
||||
# wireguard_address?} objects. Consumed by hive-agent::identity::peers()
|
||||
# + the dashboard's peer_hives StateSnapshot field (P33RS tab).
|
||||
# `cert_fingerprint` is null for CA-trusted hives; `wireguard_address`
|
||||
# is omitted when not part of the mesh.
|
||||
# wireguard_address?} objects. Consumed by hive-agent::identity::peers().
|
||||
# `cert_fingerprint` is currently unconsumed (was read only by the
|
||||
# per-hive dashboard's now-removed "peer hives" display — see
|
||||
# docs/swarm/README.md's certFingerprint note); still emitted here
|
||||
# since the shape is shared with `wireguard_address`, which is not
|
||||
# dead. `cert_fingerprint` is null for CA-trusted hives;
|
||||
# `wireguard_address` is omitted when not part of the mesh.
|
||||
#
|
||||
# Reads `peerHives` — `swarm.hives` minus this hive — so the "not me"
|
||||
# filter is the one derived in ../swarm.nix rather than a fifth copy.
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
# The WireGuard inter-hive mesh for the local host. Split out of
|
||||
# ./swarm.nix because the two are different concerns with different
|
||||
# audiences: that file declares WHO the peers are (data hive-c0re
|
||||
# serialises into HYPERHIVE_PEERS and the dashboard renders), while
|
||||
# this one is plain host networking that a machine which runs no hive
|
||||
# at all --- the snapshot store, for one --- still needs.
|
||||
# serialises into HYPERHIVE_PEERS for agent identity), while this one
|
||||
# is plain host networking that a machine which runs no hive at all
|
||||
# --- the snapshot store, for one --- still needs.
|
||||
#
|
||||
# The two stay coupled by data, not by structure: the per-peer
|
||||
# `wireguard*` fields live on the peer submodule in ./swarm.nix, since
|
||||
|
|
|
|||
|
|
@ -11,7 +11,8 @@
|
|||
# detected it. One entry per hive makes that unrepresentable.
|
||||
#
|
||||
# Consumed by hive-c0re's environment (HYPERHIVE_PEERS — see
|
||||
# ./hive-c0re), identity.rs + the dashboard's P33RS tab, and the mesh in
|
||||
# ./hive-c0re), identity.rs, swarm-controller's own hive directory (its
|
||||
# `/api/hives`, swarm-controller.nix), and the mesh in
|
||||
# ./swarm-wireguard.nix. The mesh lives there rather than here because
|
||||
# bringing up an interface is host networking rather than swarm
|
||||
# bookkeeping, and a host that runs no hive still needs it.
|
||||
|
|
|
|||
Loading…
Reference in a new issue