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/credentials.md: restore the new-vs-existing progressive-enhancement split

Browse source 
The rewrite in #4445 flattened this section's new-functionality-vs-
existing-functionality split into unconditional rules, because it had
been anchored to the current-state table that PR deleted. Restore the
split on its own terms, per #4445's own description of the rule: new
functionality has to match the target shape immediately; existing
functionality can move step by step, provided each step moves toward
the target shape.

Refs #4445
This commit is contained in:
atlas 2026-09-17 00:02:00 +02:00
commit b71ff90661
1 changed files with 6 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/swarm/credentials.md
View file

@ -56,7 +56,12 @@ strategy for every credential, including the mTLS leaf.
| `swarm/services/<clientId>/oidc/client` | authelia | the service process that presents the client secret, under the certificate of the host it runs on | must be stated |
| _(not in the store)_ the mTLS client leaf | the store's own PKI, or an operator placing it by hand | its own client, off disk — the sole exception above, because it's what makes every other row's pull possible | must be stated |
## Touching a credential
## Progressive enhancement
New functionality has to match this shape immediately — no PR introducing a
credential gets a pass on any of the rules below. Existing functionality can
be moved step by step, as long as each individual step moves toward the
target shape; a step that doesn't isn't allowed just because it's existing.
A pull request that touches a credential can't: