nix: finish the current-behaviour comment sweep in touched files
Rewrite the remaining narration in files the previous commit touched: "moved"/"sat"/"was REMOVED"/"old default" comments in swarm-bao, swarm-otel, glue-bao-tls, nats-authelia, swarm-controller, swarm-ui, swarm-otel-service, swarm-authelia-service, the deploy.nix rename table, hive-ci, hive-forge/service, hive-tls, hyperhive, swarm-nats, swarm.nix and a few module-eval fixtures, so each says where a thing is or why it is so now. Revert the comment edits inside shell script strings in hive-tls, swarm-nats and the forge token mint to their previous text, so those generated units are unchanged. The only unit still changing is swarm-bao-pki (two comment lines in its script). Refs #3902
This commit is contained in:
parent
1c90619fbb
commit
e990e9a0be
21 changed files with 102 additions and 103 deletions
|
|
@ -98,10 +98,8 @@ in
|
|||
swarm's domain, not this hive's, because a swarm runs **one**
|
||||
forge that every hive in it talks to.
|
||||
|
||||
⚠️ A deployment that was running before this moved keeps its
|
||||
current name by pinning it here:
|
||||
`forge.''${services.hyperhive.domain}`, which is exactly what
|
||||
the old default rendered. Certificates follow either way: the
|
||||
⚠️ To use the per-hive name `forge.''${services.hyperhive.domain}`
|
||||
instead, pin it here. Certificates follow either way: the
|
||||
swarm-services sub-CA is name-constrained to the configured
|
||||
names (see `./swarm-ca.nix`), not to a fixed tree.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue