Automate Secret Rotation with a Cron Job
Schedule a rotation job that generates a new secret, updates consumers, and verifies the old one is revoked within one hour.
Task
Implement gh secret set DB_PASSWORD --body $(openssl rand -base64 32) && kubectl rollout restart deploy/api to close a known attack surface before the next security review finds it.
When to use this
A penetration test report flags the missing gh secret set DB_PASSWORD --body $(openssl rand -base64 32) && kubectl rollout restart deploy/api as a medium-severity finding on a public endpoint.
Prerequisites
- A running application with the vulnerable endpoint
- Access to security headers or middleware config
Steps
1. Configure gh secret set DB_PASSWORD --body $(openssl rand -base64 32) && kubectl rollout restart deploy/api in the project configuration file with the recommended defaults.
gh secret set DB_PASSWORD --body $(openssl rand -base64 32) && kubectl rollout restart deploy/api
Expected output: The configuration is accepted and gh secret set DB_PASSWORD --body $(openssl rand -base64 32) && kubectl rollout restart deploy/api runs without errors on the first invocation.
2. Run the check locally to verify gh secret set DB_PASSWORD --body $(openssl rand -base64 32) && kubectl rollout restart deploy/api produces the expected result before pushing.
pnpm test
Expected output: Local run matches CI behavior; no surprises after push.
3. Add the gate to the CI pipeline so gh secret set DB_PASSWORD --body $(openssl rand -base64 32) && kubectl rollout restart deploy/api blocks merge on failure.
- name: Run add secrets rotation automation
run: pnpm test
Expected output: Pull requests with failing gh secret set DB_PASSWORD --body $(openssl rand -base64 32) && kubectl rollout restart deploy/api are blocked from merging.
Troubleshooting
Problem
The check passes locally but fails in CI
Solution
Pin dependency versions and the runtime to match CI exactly; reproduce with the same Docker image or act.
Problem
Configuration is rejected with a schema error
Solution
Check the tool version matches the config schema; older versions may not support newer fields.
Limitations
- The gate only runs on events that trigger the workflow; locally pushed commits bypass it.
- Configuration drift is possible if someone edits settings outside version control.
Close the attack surface
Start by measuring the problem. Schedule a rotation job that generates a new secret, updates consumers, and verifies the old one is revoked within one hour. The most common mistake is adding the gate without first confirming it catches the issue you care about. Run gh secret set DB_PASSWORD –body $(openssl rand -base64 32) && kubectl rollout restart deploy/api against the current codebase and inspect the output before wiring it into CI.
gh secret set DB_PASSWORD --body $(openssl rand -base64 32) && kubectl rollout restart deploy/apiVerify and monitor
Once the gate is in place, make failures actionable. A failing gh secret set DB_PASSWORD –body $(openssl rand -base64 32) && kubectl rollout restart deploy/api should point to the exact file and line, not a generic error. Pin the tool version in the lockfile so a upstream release does not silently change behavior. Review the gate output in every pull request just like a test result.