feat(secrets): make SMTP_PASSWORD Group-2-only (BUNYIP-529) #527
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/BUNYIP-529-smtp-group2-only"
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?
Per David:
SMTP_PASSWORDis sourced only from the Group-2 Infisical runtime fetch (or theemail_configDB row), never a Group-1 file/sync secret. This removes it from every Group-1 site so Infisical is the sole runtime source.Removed from Group-1 (completeness sweep: 11 sites / 5 files)
compose.yml: thesmtp_passwordsecret definition, theSMTP_PASSWORD_FILEenv, and the service secrets-list entry; the email comment now points at Group-2.scripts/sync-secrets.nu: theSECRET_MAPentry, and the self-test's empty-optional-key example (switched toFORGEJO_API_TOKEN).scripts/init-secrets.nu: the dev-throwaway generator line..env.example: theSMTP_PASSWORDcomment, the secret-files list, and the DEV-ONLY var list.docs/secrets-infisical.md: the/bunyip/apptable row, the dual-source note, and the source-precedence section (rewritten for Group-2-only).Kept (correctly not Group-1)
The
config.rsslot (secret_env("SMTP_PASSWORD"), which the Infisical fetch fills), the DBemail_configprecedence, theemail_config.smtp_passwordat-rest column, and the Infisical fetch itself.Validation
scripts/sync-secrets.nu --self-test: 16 checks pass (theSECRET_MAPnow derives consistently fromcompose.yml; this self-test runs in CI'scheck.yml).Precedence now
DB
email_configrow > a stray plainSMTP_PASSWORDenv (e.g. one left in a SOPS file) > Infisical fetch. With no DB row and no stray value, Infisical is the source.Companion to DEV-581 (the c-01 SOPS
SMTP_PASSWORDwas already removed by the operator). Decision recorded in BUNYIP-529.