vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

docs/swarm/secrets.md: fix sense-mis-attribution in certificateFiles rewrite

Browse source 
argus caught it on PR #4557 review: 'certificateFiles reads at system
build time' hands the option itself a verb it can't perform. The
system reads the option's value at build time, not the other way
around.
This commit is contained in:
iris 2026-09-20 02:35:59 +02:00 • committed by mara
commit 9fac33a026
1 changed files with 4 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/swarm/secrets.md
View file

@ -318,9 +318,10 @@ Whatever holds the swarm root is therefore what makes swarm-service certificates
possible at all. Two things follow: possible at all. Two things follow:
- **The root's private key is a runtime file and must never enter the nix - **The root's private key is a runtime file and must never enter the nix
store**, so nothing build-time can name it — `security.pki.certificateFiles` store**, so nothing build-time can name it — the system reads
reads at system build time, and is the wrong tool here. Trust reaches `security.pki.certificateFiles`' value at build time, which makes it the
containers through a bind-mounted bundle assembled at boot instead. wrong tool here. Trust reaches containers through a bind-mounted bundle
assembled at boot instead.
- **On any topology other than all-local, placing that key is an operations - **On any topology other than all-local, placing that key is an operations
decision**, not something this module tree makes for you. A hive that hosts no decision**, not something this module tree makes for you. A hive that hosts no
swarm services needs only the root's _cert_, to trust what others issue. swarm services needs only the root's _cert_, to trust what others issue.