infisical/ai-skills

infisical-secret-rotation

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.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/infisical/ai-skills --skill infisical-secret-rotation

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

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 expiryinfisical-dynamic-secrets — not this skill
An existing, long-lived credential replaced on a schedule, staying at a stable secret paththis skill
To push Infisical secrets out to a third-party serviceinfisical-secret-syncs
To create the App Connection a rotation depends oninfisical-app-connections
Rotating a privileged/human account with session recording and checkoutinfisical-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

  1. Confirm rotation is the right feature (see the table above)
  2. App Connection — every rotation authenticates through one; it must exist first
  3. Provider — pick the rotation type
  4. Parameters — provider-specific, and for SQL the two-user setup
  5. Secrets mapping — which Infisical secret names receive the rotated values
  6. Schedule — rotationInterval (days) and rotateAtUtc
  7. Rotation model — confirm whether this provider is dual-phase or single-phase, because it changes the operational advice

Reference files

FileWhen to read
references/rotation-overview.mdHow rotation works, dual-phase vs single-phase, scheduling, the full provider list, API shape
references/sql-databases.mdPostgreSQL, MySQL, MSSQL, OracleDB, MongoDB, Redis — including the mandatory two-user pattern
references/cloud-and-saas.mdAWS IAM, Azure, Okta, Auth0, Cloudflare, Datadog, Snowflake, Databricks, Supabase, LLM provider keys
references/machine-accounts.mdLDAP 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 postgres connection, not a generic one). See infisical-app-connections.
  • SQL rotations need two pre-existing users. This is the single most common setup failure. Infisical alternates between username1 and username2; 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.
  • `rotationInterval` is 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.

Verwandte Aufgaben

aus demselben Repository

Weitere Skills

Alle Skills
infisical
Community

infisical-access-control

Guide for Infisical access control and governance — org and project roles, custom roles with subject/action permissions, granular secret permissions that separate describing a secret from reading its value, attribute-based access control (ABAC) driven by user metadata and machine identity attributes, additional privileges, assume-privilege, temporary (time-bound) access, access requests, change-approval and access-approval policies, and audit logs including streaming to Splunk, Datadog, Azure, C

Installationen / 1h
1
GitHub Stars
41
Aktualisiert
11. Nov.
infisical
Community

infisical-agent

Guide for configuring the Infisical Agent — a client daemon that manages token lifecycle and renders secrets via Go templates without modifying application code. Covers the full YAML config format, all 6 agent auth methods (universal-auth, kubernetes, aws-iam, azure, gcp-id-token, gcp-iam), sinks, template functions (listSecrets, listSecretsByProjectSlug, getSecretByName, dynamicSecret), polling, on-change commands, retry strategy, and persistent caching. Use this skill when someone asks about:

Installationen / 1h
1
GitHub Stars
41
Aktualisiert
11. Nov.
infisical
Community

infisical-api

Interact with the Infisical REST API to manage secrets, projects, environments, machine identities, and more. Supports secret CRUD operations, machine identity authentication, pagination, and rate limiting on cloud deployments. Not for the CLI/SDKs (infisical-setup), KMS crypto endpoints (infisical-kms), certificate endpoints (infisical-pki), or human SSO login (infisical-sso).

Installationen / 1h
1
GitHub Stars
41
Aktualisiert
11. Nov.
infisical
Community

infisical-app-connections

Guide for creating and managing Infisical App Connections — the reusable authenticated links between Infisical and third-party services that Secret Syncs, Secret Rotations, PKI certificate authorities, PKI Syncs, and Secret Scanning data sources all depend on. Covers all 83 connection types and their exact auth methods (AWS assume-role vs access-key, GitHub OAuth vs GitHub App vs PAT, Azure OAuth vs client-secret vs certificate, GCP service account impersonation, and more), platform-managed cred

Installationen / 1h
1
GitHub Stars
41
Aktualisiert
11. Nov.