chore(secrets): retire sync-secrets.nu; Group-1 not from Infisical (BUNYIP-531) #529
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/BUNYIP-531-retire-sync-secrets"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Group-1 startup secrets come from the compose secrets file (the SOPS
compose-secrets.ymlon the docker hosts) orinit-secrets.nuin dev, never Infisical. Only Group-2 integration secrets (SMTP,/runtime) use Infisical. This removes the Group-1-from-Infisical mechanism, reversing BUNYIP-504.Removed
scripts/sync-secrets.nu(the Infisical -> Group-1 file renderer).check.ymlself-test step and thejust sync-secretsrecipe.Docs rewritten (Group-1 = compose secrets file / init-secrets, not Infisical)
docs/secrets-infisical.md(retitled, Group-1 section is now file/SOPS; only Group-2 plus the E2E credential live in Infisical),CLAUDE.md,README.md, thecompose.ymlheader,scripts/init-secrets.nu,docs/getting-started.md,docs/e2e.md.Unaffected
The E2E password (Infisical
/bunyip/e2e) is a test credential, not a Group-1 startup secret.Note
docs/e2e.mdpreviously cited BUNYIP-505 ("move the c-01 secret source off sops and the CI secrets onto Infisical"), which contradicts this direction (Group-1 stays in SOPS); the reference is dropped. BUNYIP-505 likely needs closing or revising.Companion doc updates: docker runbook + governance
INFISICAL.md. BUNYIP-530 (migrate Group-1/bunyip/app->/app) is now obsolete and will be closed.