| Filename | Latest commit message | Latest commit date |
|---|---|---|
e71c9cc431
The test named for pinning the external tag covered all but the newest variant, and two doc comments still counted three outcomes where there are four. Folded the missing variant in rather than editing the number: a test that claims to settle the wire shape and quietly omits one is worse than a narrower one, because the next variant gets added with nothing to point its author here. The counts are gone rather than corrected — prose that counts its subject is falsified by every addition and is invisible to a grep for the vocabulary that changed. |
||
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
swarm-authelia-bridge-sock
Wire types for the swarm-authelia-bridge socket — the contract between
swarm-authelia-bridge (server, runs alongside swarm-authelia) and
swarm-controller (client).
Why it's its own crate
Same rationale as hive-priv-sock (which this mirrors in spirit, though the
transport differs — this bridge is network-facing HTTP, not a unix socket,
since it has to reach a possibly-split-host swarm-controller): the bridge
is a narrowly-scoped, unprivileged-but-file-owning helper, and splitting the
wire contract out of any larger crate keeps both its own dependency
footprint and its interface small enough to audit at a glance. No server or
client logic here, only the request/response shapes both sides import.
Shape
Two operations: idempotently ensure an agent exists as an authelia subject,
and list the ones that do. Deliberately not a wholesale-replace-the-file API — the bridge
reads users.yml, changes what the request named, and writes it back; a
caller only ever asks for one user to exist, never sends rendered YAML or a
file blob. See swarm-authelia-bridge/README.md for the helper itself.