3202cde704
`services.hyperhive.enable` and `services.hyperhive.c0re.enable` are gone. One switch, `services.hyperhive.deploy.hive-controller.enable` (default false, as the old toggle was), now gates hive-c0re and hive-priv. Both old paths are `mkRenamedOptionModule` shims in deploy.nix, so a host config that still sets either evaluates as before and gets a rename warning. Every other read of the old toggle is resolved, including the 29 made through the `hyperhiveCfg`/`hiveCfg` aliases: - Dropped: each swarm service and its glue keeps only its own deploy toggle (authelia, bao and its PKI glue, grafana, victorialogs, victoriametrics, the secret publisher, swarm-ca, the OIDC client rows, the controller/nats/matrix-ctl/publisher/services-issuer identities), the forge, and the `domain` deprecation warning. - To deploy.hive-controller.enable: the queue-agent credential reader and its assertion, which feed hive-c0re and write under its state dir, plus their policy-order entry; the network identity assertions; hive-tls's two writes into hive-c0re's environment. - hive-tls runs where the gateway runs self-signed (`gateway.enable && useSelfSigned`), not on every host. - The matrix appservice-token reader and its assertion stay on `deploy.matrix.enable` plus their client-identity checks. They read deploy.matrix's token file and registration script; their deploy.bao inputs are the client-half options a hive sets to read a store it does not run, so gating on deploy.bao.enable would drop the tested remote-reader case. - The `hiveName` assertion moves from hive-network.nix to hyperhive.nix and fires wherever the hive, the store or the homeserver runs: each turns the name into an identifier with no fallback. On a host with `deploy.allSwarmServices` and no hive, the documented services-host recipe, authelia, bao, grafana, victorialogs, victoriametrics, the OIDC client rows and the hive CA now render; before, the old toggle being off left them out. Refs #4500
40 lines
1.5 KiB
Nix
40 lines
1.5 KiB
Nix
# Glue: register the swarm's forge as an OIDC client wherever authelia runs.
|
|
#
|
|
# ONE PAIRING PER FILE — forge ← authelia, and nothing else. Deleting this
|
|
# leaves a swarm whose forge is not a client authelia has ever heard of, so
|
|
# its "sign in with" button can never complete a login and nothing minted its
|
|
# secret either.
|
|
#
|
|
# ⚠️ Gated on authelia being HERE, and deliberately NOT on this host running
|
|
# the forge. A client is a row in THIS host's provider config, so it can only be
|
|
# declared where that config is rendered — and ./hive-forge/default.nix's whole
|
|
# `config` block hangs off `deploy.forgejo.enable`, so a swarm with the forge
|
|
# and authelia on different hosts would register the client nowhere at all.
|
|
# Same shape as ./glue-grafana-oidc-client.nix, for the same reason.
|
|
#
|
|
# Unlike Grafana's, this client is never unused: every swarm runs a forge.
|
|
{
|
|
lib,
|
|
config,
|
|
...
|
|
}:
|
|
let
|
|
hyperhiveCfg = config.services.hyperhive;
|
|
deployCfg = hyperhiveCfg.deploy;
|
|
forgeCfg = hyperhiveCfg.swarm.forge;
|
|
in
|
|
{
|
|
config = lib.mkIf deployCfg.authelia.enable {
|
|
# One declaration, two readers. The forge knows its own callback URL;
|
|
# making the operator restate it in authelia's client list would be a
|
|
# second source of truth for a string whose mismatch is a silent
|
|
# rejected login.
|
|
services.hyperhive.swarm.authelia.oidc.clients = [
|
|
{
|
|
id = forgeCfg.sso.clientId;
|
|
description = "HyperHive forge";
|
|
redirectUris = [ forgeCfg.sso.redirectUri ];
|
|
}
|
|
];
|
|
};
|
|
}
|