infisical/ai-skills

infisical-terraform

Expert guidance for the Infisical Terraform Provider.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/infisical/ai-skills --skill infisical-terraform

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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 pipelineinfisical-setup
Raw REST API calls rather than HCLinfisical-api
To push secrets to a third-party serviceinfisical-secret-syncs
On-demand ephemeral database credentialsinfisical-dynamic-secrets
Roles and permission model designinfisical-access-control
To deploy a Gateway or Relay via Terraforminfisical-gateway
To deploy Infisical itselfinfisical-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

Key principles to uphold

  1. Credentials go inside a nested `auth` attribute: the provider takes

auth = { universal = { client_id, client_secret } } or auth = { oidc = { identity_id, token_environment_variable_name } }. Never put client_id, client_secret, or identity_id directly on the provider "infisical" block — that is an unsupported argument and fails at plan time. (Legacy service_token is the one exception and does sit at the top level.)

  1. The ephemeral secret's key is `name`: ephemeral "infisical_secret" takes

name, workspace_id, env_slug, and optional folder_path. There is no secret_key argument.

  1. Ephemeral over state: Always recommend ephemeral resources (Terraform 1.10+) for secrets—values never land in state files. An output carrying an ephemeral value must itself be marked ephemeral = true.
  2. Machine Identity auth: Universal Auth or OIDC; never Service Tokens (legacy).
  3. Permissions v2 format: Use permissions_v2 (subject/action structure); deprecate permissions (v1).
  4. OIDC for Terraform Cloud: This is the recommended production pattern.
  5. Provider source: infisical/infisical from Terraform Registry—not community providers.
  6. Folder path defaults: folder_path = "/" if omitted.
  7. Self-hosted needs `host`: set the host attribute 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
같은 저장소의 Skills

더 많은 Skills

모든 Skills
infisical
커뮤니티

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

1시간 설치 수
1
GitHub Stars
41
업데이트
11월 11일
infisical
커뮤니티

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:

1시간 설치 수
1
GitHub Stars
41
업데이트
11월 11일
infisical
커뮤니티

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).

1시간 설치 수
1
GitHub Stars
41
업데이트
11월 11일
infisical
커뮤니티

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

1시간 설치 수
1
GitHub Stars
41
업데이트
11월 11일