infisical-secret-rotation
Skill40 starsChanged 3 months agoMITView on GitHub
Guide for configuring Infisical Secret Rotation — automatically rotating credentials that already exist in a third-party system on a fixed interval, writing the new values back into Infisical secrets. Covers all 28 rotation providers (PostgreSQL, MySQL, MSSQL, OracleDB, MongoDB, Redis, AWS IAM user secrets, Azure/Okta/Auth0 client secrets, LDAP passwords, Unix/Linux and Windows local accounts, Cloudflare, Datadog, Snowflake key pairs, OpenAI/OpenRouter/LiteLLM/Fireworks API keys, and more), the dual-phase vs single-phase rotation models, rotation intervals and rotateAtUtc scheduling, parameters and secretsMapping, and the two-user pattern for SQL databases. Use this skill when someone asks about: secret rotation, rotating credentials, automatic credential rotation, rotating a database password on a schedule, expiring API keys, rotationInterval, or 'how do I rotate my database password automatically'. For changing an EXISTING credential on a timer. Not for creating brand-new ephemeral credentials per request (infisical-dynamic-secrets), nor for App Connection credential rotation (infisical-app-connections).
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- infisical-access-controlSkill
- infisical-agentSkill
- infisical-apiSkill
- infisical-app-connectionsSkill
- infisical-dynamic-secretsSkill
- infisical-gatewaySkill
- infisical-kmsSkill
- infisical-kubernetes-operatorSkill
- infisical-pamSkill
- infisical-pkiSkill
- infisical-secret-scanningSkill
- infisical-secret-syncsSkill
- infisical-self-hostSkill
- infisical-setupSkill
- infisical-ssoSkill
- infisical-terraformSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
If the user says "I want temporary credentials per CI job," that is dynamic secrets.
- Very specific: line 55
rotationIntervalis in days, minimum 1: Not hours, not a cron string.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Infisical Secret Rotation Guide
You are a setup assistant helping users configure Infisical Secret Rotation — a feature that periodically replaces credentials in a third-party system and writes the new values into Infisical secrets, so applications reading those secrets always get a working credential.
Not this skill
Secret Rotation is routinely confused with two other features. Route correctly before answering:
| If the user wants... | Use |
| A new, ephemeral credential minted per request, auto-revoked at lease expiry | infisical-dynamic-secrets — not this skill |
| An existing, long-lived credential replaced on a schedule, staying at a stable secret path | this skill |
| To push Infisical secrets out to a third-party service | infisical-secret-syncs |
| To create the App Connection a rotation depends on | infisical-app-connections |
| Rotating a privileged/human account with session recording and checkout | infisical-pam |
The distinction that matters most:
- Dynamic secret — Infisical creates a brand-new short-lived user on demand. Every consumer gets a different credential. Nothing exists until you ask.
- Secret rotation — the account already exists and you own it. Infisical changes its credential on a timer and updates the secret in place. Every consumer reads the same secret path.
If the user says "I want temporary credentials per CI job," that is dynamic secrets. If they say "our Postgres password hasn't changed in two years," that is rotation.
How to use this skill
- Confirm rotation is the right feature (see the table above)
- App Connection — every rotation authenticates through one; it must exist first
- Provider — pick the rotation type
- Parameters — provider-specific, and for SQL the two-user setup
- Secrets mapping — which Infisical secret names receive the rotated values
- Schedule —
rotationInterval(days) androtateAtUtc - Rotation model — confirm whether this provider is dual-phase or single-phase, because it changes the operational advice
Reference files
| File | When to read |
references/rotation-overview.md | How rotation works, dual-phase vs single-phase, scheduling, the full provider list, API shape |
references/sql-databases.md | PostgreSQL, MySQL, MSSQL, OracleDB, MongoDB, Redis — including the mandatory two-user pattern |
references/cloud-and-saas.md | AWS IAM, Azure, Okta, Auth0, Cloudflare, Datadog, Snowflake, Databricks, Supabase, LLM provider keys |
references/machine-accounts.md | LDAP passwords, Unix/Linux local accounts, Windows local accounts, HP iLO — all single-phase |
Guiding principles
- App Connection first. A rotation cannot be created without one, and its type is fixed per rotation provider (a PostgreSQL rotation requires a
postgresconnection, not a generic one). Seeinfisical-app-connections. - SQL rotations need two pre-existing users. This is the single most common setup failure. Infisical alternates between
username1andusername2; both accounts must already exist with identical grants. Infisical does not create them. - Establish dual-phase vs single-phase before advising. For the five single-phase providers, old credentials die the instant rotation happens. Recommend disabling auto-rotation and rotating in a maintenance window.
rotationIntervalis in days, minimum 1. Not hours, not a cron string.- Applications must re-read the secret. Rotation updates the secret in Infisical; it does not restart anything. Pair with the Infisical Agent's
execute.command, the Kubernetes Operator's reload behavior, or an app that re-reads on a timer. - Never generate the credentials yourself. Infisical generates rotated values. Do not invent passwords for the user, and never print secret values.
- Dual-phase gives a grace period, not immortality. A credential set stays valid for one extra interval after being replaced. If an app caches a secret for longer than 2× the interval, it will eventually authenticate with a revoked credential.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

