infisical-terraform
Skill36 starsChanged 3 months agoMITView on GitHub
Expert guidance for the Infisical Terraform Provider. Covers HCL resource configuration, ephemeral secrets management, data source patterns, project role permissions, and OIDC authentication for Terraform Cloud. Use for secret injection via IaC, Machine Identity setup, access approval policies, and cloud-native integration patterns. Not for getting secrets into a running app (infisical-setup) or raw REST calls (infisical-api).
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-rotationSkill
- infisical-secret-scanningSkill
- infisical-secret-syncsSkill
- infisical-self-hostSkill
- infisical-setupSkill
- infisical-ssoSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 60
Ephemeral over state: Always recommend ephemeral resources (Terraform 1.10+) for secrets—values never land in state files.
- Very specific: line 62
Permissions v2 format: Use permissions_v2 (subject/action structure).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Terraform Provider
Help users confidently integrate Infisical secret management with their Terraform infrastructure.
Not this skill
| If the user wants... | Use |
| To get secrets into a running app, container, or pipeline | infisical-setup |
| Raw REST API calls rather than HCL | infisical-api |
| To push secrets to a third-party service | infisical-secret-syncs |
| On-demand ephemeral database credentials | infisical-dynamic-secrets |
| Roles and permission model design | infisical-access-control |
| To deploy a Gateway or Relay via Terraform | infisical-gateway |
| To deploy Infisical itself | infisical-self-host |
This skill is about the Infisical Terraform provider — managing Infisical resources and reading secrets from HCL. It is not about using Terraform generally.
What users typically ask for
- "How do I use Infisical with Terraform?" — Provider setup and auth
- "How do I prevent secrets in my Terraform state?" — Ephemeral resources
- "How do I set up Terraform Cloud with Infisical?" — OIDC integration
- "How do I configure project roles and permissions?" — Role definitions
- "What's the difference between ephemeral and data sources?" — Resource patterns
Quick routing
- Provider authentication, configuration, env vars → Provider Setup
- HCL resources: infisical_secret, data sources, project roles, access approval → Resources & Data Sources
- Terraform Cloud OIDC integration, machine identity setup → Terraform Cloud OIDC
Key principles to uphold
- Credentials go inside a nested
authattribute: the provider takesauth = { universal = { client_id, client_secret } }orauth = { oidc = { identity_id, token_environment_variable_name } }. Never putclient_id,client_secret, oridentity_iddirectly on theprovider "infisical"block — that is an unsupported argument and fails at plan time. (Legacyservice_tokenis the one exception and does sit at the top level.) - The ephemeral secret's key is
name:ephemeral "infisical_secret"takesname,workspace_id,env_slug, and optionalfolder_path. There is nosecret_keyargument. - Ephemeral over state: Always recommend
ephemeralresources (Terraform 1.10+) for secrets—values never land in state files. An output carrying an ephemeral value must itself be markedephemeral = true. - Machine Identity auth: Universal Auth or OIDC; never Service Tokens (legacy).
- Permissions v2 format: Use
permissions_v2(subject/action structure); deprecatepermissions(v1). - OIDC for Terraform Cloud: This is the recommended production pattern.
- Provider source:
infisical/infisicalfrom Terraform Registry—not community providers. - Folder path defaults:
folder_path = "/"if omitted. - Self-hosted needs
host: set thehostattribute on the provider block; there is no site-URL environment variable.
When to send users to references
- Auth confusion or env var setup → provider-setup.md
- Building HCL for secrets, roles, approval policies → resources-and-data-sources.md
- TFC + Infisical step-by-step → terraform-cloud-oidc.md
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.

