Add a credential docs page: current state, target state, the rule between
The swarm's credential docs say where every file lives. They do not say whether it should be a file at all, so a discussion about direction has had nothing to point at and each one re-derived the same table. This page carries that table with the three columns the target contract is written in — minter, reader, renewal — plus the column the target is really about: whether the value is persisted outside the store. Stating it flatly is the point. All four stored families are plaintext files on disk, the appservice token twice; every renewal cell reads NONE; no agent container holds a store identity at all, so the hive reads on its behalf and writes a file in; and the appservice token has a second, uncoordinated local mint that can diverge from the published one. The target section is marked as a target throughout, because its first line is the one most easily misread as fact: every host needing a store mTLS certificate is where this is going, while today only the store's own host auto-mints and swarm-bao.nix calls it the credential an operator places by hand everywhere else. The progressive-enhancement rule is stated as a table of questions a reviewer applies to a pull request rather than as prose, since a rule nobody can check is a preference. New functionality matches the target immediately; existing functionality moves stepwise, and the questions distinguish a step from churn. Indexed from the docs root and the swarm README. It supersedes secrets.md when the migration completes — at which point that file is deleted and this one moves into its place.
This commit is contained in:
parent
c3f5479ca8
commit
937289383c
3 changed files with 147 additions and 0 deletions
|
|
@ -76,6 +76,10 @@ declarations.
|
|||
- **Where do agent snapshots go? How does the swarm's `btrfs receive`
|
||||
endpoint authenticate a pushing hive?** →
|
||||
[`networking/snapshot-store.md`](networking/snapshot-store.md).
|
||||
- **Who mints each credential, who reads it, and how does it rotate — and
|
||||
where is that shape headed?** → [`swarm/credentials.md`](swarm/credentials.md)
|
||||
(current state, target state, and the progressive-enhancement rule);
|
||||
[`swarm/secrets.md`](swarm/secrets.md) for where each file lives today.
|
||||
|
||||
## Scheduler, CI, observability
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue