fix(ci): staging secrets keep valid formats for config-like keys #66
Loading…
Reference in a new issue
No description provided.
Delete branch "jfraeys/fix/staging-secrets-formats"
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?
Run 463 reached the backups role and failed:
RESTIC_REPOSITORY must be an absolute path or a backend URL ... Got: staging-unused. The generator gave every non-secret-sounding key a placeholder, which breaks roles that validate formats (restic repo, ports, schedules, retention counts, SMTP hosts).Now the manifest's 18
config:keys keep their production values, with overrides for the dangerous ones: RESTIC_REPOSITORY is a local path (staging never writes to the production bucket), the secondary repo stays off, ALERTMANAGER_EMAIL_TO is example.invalid. Empty strings stay empty (SOPS leaves them plain; hygiene check now accepts them). Re-verified: the staging key decrypts the file, is refused on the production vault, and every value equal to production is non-secret config. 🤖 Generated with Claude Code