pulumi-esc

Manage Pulumi ESC environments, secrets, and OIDC credentials via CLI commands.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/AdityaBorkar/igbot-fork --skill pulumi-esc-adityaborkar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pulumi-esc
Source: https://github.com/AdityaBorkar/igbot-fork/tree/main/.agents/skills/pulumi-esc
Command: npx skills add https://github.com/AdityaBorkar/igbot-fork --skill pulumi-esc-adityaborkar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing secrets and configuration across cloud environments is error-prone and scattered. This Skill provides guidance for centralizing secrets, composing environments, and generating short-term cloud credentials with Pulumi ESC. ## Core Features & Use Cases - Environment Management: Create, edit, and compose layered ESC environments using the pulumi env CLI commands. - Dynamic Credentials: Configure OIDC-based short-term credentials for AWS, Azure, and GCP, plus integrations with Vault, 1Password, and cloud secret stores. - Stack Integration: Link ESC environments to Pulumi stacks so pulumiConfig values flow into deployments. - Use Case: A team wants to eliminate static AWS access keys. Use this Skill to set up an ESC environment with AWS OIDC login, link it to a Pulumi stack, and verify the configuration resolves correctly. ## Quick Start Ask the assistant to create a Pulumi ESC environment for your project and link it to your Pulumi stack.

Frequently Asked Questions about pulumi-esc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Pulumi ESC environment?▼

Run `pulumi env init <org>/<project-name>/<environment-name>` to create an environment, then use `pulumi env edit` to define its YAML contents. You can set values with `pulumi env set`, using the `--secret` flag for sensitive data.

What is the difference between pulumi env get and pulumi env open?▼

`pulumi env get` shows the static environment definition with secrets masked as `[secret]`. `pulumi env open` resolves and reveals all values, including secrets and dynamic credentials, so use it only when full values are required.

How do I set up AWS OIDC credentials in Pulumi ESC?▼

Configure an AWS OIDC provider in your ESC environment following the Pulumi dynamic login credentials documentation. You need an IAM role for ESC to assume, then reference the provider in your environment's values to generate short-term credentials.

Can Pulumi ESC integrate with HashiCorp Vault or 1Password?▼

Yes, ESC integrates with external secret stores including AWS Secrets Manager, Azure Key Vault, HashiCorp Vault, and 1Password. These are configured as dynamic secret providers within the environment YAML definition.

Why can't my Pulumi stack read ESC environment values?▼

Verify the environment is linked with `pulumi config env ls` and referenced by the project-name/environment-name format only. Check that the `pulumiConfig` key exists nested under `values` in the environment definition.