Rotate secrets exposed in git history #50
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cal/paper-dynasty-card-creation#50
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
Summary
PR #29 removed hardcoded secrets from the codebase, but they remain in git history and should be rotated.
Secrets to rotate
PD API bearer token (
Tp3aO3jhYve5NJF1IqOmJTmk) — was hardcoded indb_calls.py. Regenerate in Paper Dynasty API admin.Supabase service-role JWT — was hardcoded in
scripts/supabase_doodling.py(file now deleted). JWT expiry is 2061, so it remains valid until rotated. Rotate in Supabase dashboard.After rotation
.envfile on any machine running the card pipeline with the new PD API tokenpd-cardsCLI still authenticates correctlyPriority
High — exposed credentials should be rotated promptly even though the repos are private.
Resolved via PR #52
Tp3aO3jhYve5NJF1IqOmJTmk) scrubbed fromdocs/PD_CARDS_CLI_REFERENCE.md— replaced withyour-api-token-hereplaceholderLadies5-Monogamy-Charterreferences.envis gitignored; no additional example file gap in this repoSee
paper-dynasty-database#9for full rotation details (API_TOKEN rotated on prod + dev, POSTGRES_PASSWORD verified).