grant-bootstrap re-applies the granter and restarts failed policy units; setup treats a refused granting unit as not done
This commit is contained in:
parent
ae37c228b1
commit
c7d37ca455
1 changed files with 271 additions and 33 deletions
|
|
@ -52,7 +52,13 @@ and the unit runs once. A successful run deletes the token file too.
|
|||
|
||||
After that, a new or changed `swarm-*` grant needs no operator step: the unit
|
||||
that writes it changes, and the deploy restarts it. A root step comes back only
|
||||
when the granter itself needs a path it lacks, such as a new mount.
|
||||
when the granter itself needs a path it lacks, such as a new mount. That
|
||||
step is `swarmctl bao grant-bootstrap`, which is also the re-apply: a change
|
||||
to `granterPolicyText` or to `bao-bootstrap-policy.hcl` reaches an existing
|
||||
store only through it, since the deploy leaves the store's copy alone. It
|
||||
writes `bao-bootstrap`, places a fresh 24h token, restarts the granter unit
|
||||
(which rewrites `bao-granter`), then resets and restarts the failed
|
||||
`swarm-bao-*-policy` units.
|
||||
|
||||
⚠️ The granting units re-run on **boot** and whenever a deploy **changes**
|
||||
them, not on every deploy. When a grant drifts in the store and its unit stays
|
||||
|
|
|
|||
Loading…
Reference in a new issue