ops: update option pointers after otel split
Four comments pointed at ./swarm-otel.nix for something the split moved to ./swarm-otel-service.nix: `domain` (otel.nix), `domainBase` (swarm-ui.nix), the `clientId`/`audience` options (glue-swarm-otel-oidc-client.nix), and `producerName` (swarm-otel.nix's own "Read-only option below"). Every other pointer to ./swarm-otel.nix names its `config` block, units, exporters, authenticators or assertions, which stayed. Refs #3742
This commit is contained in:
parent
3a0a7346b1
commit
a5eb3c15c4
4 changed files with 9 additions and 9 deletions
|
|
@ -35,10 +35,10 @@ let
|
|||
# that reserves it is checking the same string the config emits. A literal
|
||||
# repeated at each site would let the guard and the config drift apart, which
|
||||
# is the failure this guard exists to prevent.
|
||||
# Read-only option below, not a bare literal — `swarm-controller.nix` needs
|
||||
# the identical string to build the same audience/endpoint, and a value
|
||||
# bound once here (rather than copy-pasted at both sites) is the only way
|
||||
# the two can't drift apart.
|
||||
# The read-only `producerName` option in ./swarm-otel-service.nix, not a bare
|
||||
# literal — `swarm-controller.nix` needs the identical string to build the
|
||||
# same audience/endpoint, and a value bound once (rather than copy-pasted at
|
||||
# both sites) is the only way the two can't drift apart.
|
||||
swarmTierName = cfg.producerName;
|
||||
|
||||
# The SECOND swarm-tier producer: the collector inside the secret store's
|
||||
|
|
|
|||
Loading…
Reference in a new issue