Stabilize forgejo namespace auth and secrets
This commit is contained in:
parent
5c0a9b3f54
commit
5b09f3a742
8 changed files with 59 additions and 49 deletions
|
|
@ -158,10 +158,11 @@ instances:
|
|||
For Burrow, use `Scripts/provision-forgejo-nsc.sh` to mint the Forgejo PAT,
|
||||
generate a Namespace token from the logged-in Namespace account, and refresh
|
||||
`secrets/forgejo/{nsc-token,nsc-dispatcher-config,nsc-autoscaler-config}.age`.
|
||||
The token file is emitted as JSON with a `bearer_token` field so both the
|
||||
Compute API path and the `nsc` CLI fallback can consume the same secret
|
||||
material. The forge host consumes the encrypted secrets through agenix; avoid
|
||||
keeping local plaintext `intake/` copies around.
|
||||
The token file is emitted as JSON with a long-lived `session_token` plus the
|
||||
current `bearer_token`. The `nsc` CLI paths use the session-backed login flow,
|
||||
while the Compute API path can consume the bearer token directly. The forge
|
||||
host consumes the encrypted secrets through agenix; avoid keeping local
|
||||
plaintext `intake/` copies around.
|
||||
|
||||
Long-lived runtime state is now sourced from age-encrypted files:
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue