Pulumi Esc
PulumiOfficialPublished by Pulumi
- Skill
- Tool integration
- Cloud and DevOps
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
Pulumi ESC is a centralized service designed to manage environments, secrets, and configuration across cloud infrastructure. It allows teams to compose environments through layering, generate dynamic credentials via OIDC for major cloud providers, and integrate with external secret stores like AWS Secrets Manager, Azure Key Vault, and 1Password. The skill provides instructions on using the CLI to initialize, edit, and link environments to Pulumi stacks, ensuring secure and audited configuration management.
What it does
- Centralizes secrets and configuration in a secure location
- Composes environments by importing and layering configurations
- Generates dynamic credentials using OIDC for AWS, Azure, and GCP
- Integrates with external secret stores like HashiCorp Vault and 1Password
- Links environments to Pulumi stacks for automated configuration injection
- Provides versioning and auditing for all configuration changes
When to use it
- When you need to manage secrets and configuration across multiple cloud environments
- When you want to replace static credentials with dynamic OIDC-based authentication
- When you need to share configuration values across different Pulumi stacks
- When you need to integrate external secret managers into your infrastructure workflow
- When you need to audit and version control your environment configurations
Advantages
- Reduces reliance on long-lived static credentials
- Simplifies configuration management through environment composition
- Provides a unified interface for secrets and cloud configuration
- Enhances security with fine-grained RBAC and audit logs
- Seamlessly integrates with existing Pulumi stack workflows
Usage examples
- “How do I create a new Pulumi ESC environment?”
- The agent will guide you to use the pulumi env init command followed by the organization, project, and environment name.
- “How can I link an ESC environment to my existing Pulumi stack?”
- The agent will explain how to use pulumi config env add to associate the environment with your stack, ensuring you confirm the change before execution.
- “How do I set up AWS OIDC credentials in ESC?”
- The agent will provide the necessary configuration steps and guide you through setting up the OIDC provider integration.
- “What is the difference between pulumi env get and pulumi env open?”
- The agent will clarify that get shows the static definition with hidden secrets, while open resolves and reveals all values including secrets.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/pulumi/pulumi-esc/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip pulumi-esc.zip -d .agents/skills
Documentation by Pulumi
Pulumi ESC (Environments, Secrets, and Configuration)
Pulumi ESC is a centralized service for managing environments, secrets, and configuration across cloud infrastructure and applications.
What is ESC?
ESC enables teams to:
Centralize secrets and configuration in one secure location
Compose environments by importing and layering configuration
Generate dynamic credentials via OIDC for AWS, Azure, GCP
Integrate external secret stores (AWS Secrets Manager, Azure Key Vault, Vault, 1Password)
Version and audit all configuration changes
Control access with fine-grained RBAC
Essential CLI Commands
# Create a new environment
pulumi env init <org>/<project-name>/<environment-name>
# Edit environment (opens in editor)
pulumi env edit <org>/<project-name>/<environment-name>
# Set values
pulumi env set <org>/<project-name>/<environment-name> <key> <value>
pulumi env set <org>/<project-name>/<environment-name> <key> <value> --secret
# View definition (secrets hidden)
pulumi env get <org>/<project-name>/<environment-name>
# Open and resolve (reveals secrets)
pulumi env open <org>/<project-name>/<environment-name>
# Run command with environment
pulumi env run <org>/<project-name>/<environment-name> -- <command>
# Link to Pulumi stack
pulumi config env add <project-name>/<environment-name>Key Concepts
Command Distinctions
pulumi env get: Shows static definition, secrets appear as[secret]pulumi env open: Resolves and reveals all values including secrets and dynamic credentialspulumi env run: Executes commands with environment variables loadedpulumi config env add: Only takes the <project-name>/<environment-name> portion
Environment Structure
Environments are YAML documents with reserved top-level keys:
imports: Import and compose other environmentsvalues: Define configuration and secrets
Reserved sub-keys under values:
environmentVariables: Map values to shell environment variablespulumiConfig: Configure Pulumi stack settingsfiles: Generate files with environment data
Basic Example
imports:
- common/base-config
values:
environment: production
region: us-west-2
dbPassword:
fn::secret: super-secure-password
environmentVariables:
AWS_REGION: ${region}
DB_PASSWORD: ${dbPassword}
pulumiConfig:
aws:region: ${region}
app:dbPassword: ${dbPassword}Reading Another Stack's Outputs
Use the fn::open::pulumi-stacks provider to consume another stack's outputs. The
stacks and network keys below are arbitrary names you choose. Once the function
resolves, it replaces stacks.network with the named stack's outputs — so the
output names (vpcId, subnetIds) do not appear in the static YAML; they come from
whatever the producer stack exports. Two things are easy to get wrong:
The stack is named by a single project-qualified
stack: <project>/<stackName>field — not separateprojectName/stackNamefields.Outputs resolve directly under the stack name — there is no
.outputs.level (use${stacks.network.vpcId}, not${stacks.network.outputs.vpcId}).
Example — replace the stack name and output names with your own:
values:
stacks:
fn::open::pulumi-stacks:
stacks:
network: # arbitrary local name for the referenced stack
stack: my-project/dev # producer stack to read outputs from
pulumiConfig:
# vpcId / subnetIds are whatever the producer stack exports; after the function
# resolves they are available directly under `stacks.network` (no `.outputs.`).
vpcId: ${stacks.network.vpcId}
subnetIds: ${stacks.network.subnetIds}Full schema: https://www.pulumi.com/docs/esc/providers/pulumi-stacks/
Viewing an Environment in the Pulumi Cloud Console
The console URL for an environment is
https://app.pulumi.com/<org>/esc/<project>/<environment>. The route segment is
esc, not environments.
Working with the User
For Simple Questions
If the user asks basic questions like "How do I create an environment?" or "What's the difference between get and open?", answer directly using the information above.
For Detailed Documentation
When users need more information, use the web-fetch tool to get content from the official Pulumi ESC documentation:
Complete YAML syntax and functions → https://www.pulumi.com/docs/esc/environments/syntax/
Provider integrations (AWS, Azure, GCP, Vault, 1Password):
AWS: https://www.pulumi.com/docs/esc/integrations/dynamic-login-credentials/aws-login/
Azure: https://www.pulumi.com/docs/esc/integrations/dynamic-login-credentials/azure-login/
GCP: https://www.pulumi.com/docs/esc/integrations/dynamic-login-credentials/gcp-login/
Short-term credential (OIDC) providers: https://www.pulumi.com/docs/esc/integrations/dynamic-login-credentials/
Dynamic secret providers: https://www.pulumi.com/docs/esc/integrations/dynamic-secrets/
Pulumi stack outputs (
fn::open::pulumi-stacks): https://www.pulumi.com/docs/esc/providers/pulumi-stacks/All providers (index): https://www.pulumi.com/docs/esc/providers/
Getting started guide → https://www.pulumi.com/docs/esc/get-started/
CLI reference → https://www.pulumi.com/docs/esc/cli/commands/
Prefer using the
pulumi envsubcommands overescCLI.
Use the web-fetch tool with specific prompts to extract relevant information from these docs.
For Complex Tasks
When helping users:
Understand the goal: Are they setting up new environments, migrating from stack config, or debugging?
Check existing setup: Use
pulumi envcommands to list environments or read definitionsFetch relevant documentation: Use the web-fetch to get specific examples or syntax from the official docs
Provide step-by-step guidance: Walk through the process with specific commands
Validate: Help them test with
pulumi env getorpulumi previewa. Only usepulumi env openwhen the full resolved values are needed, but use cautiously as it reveals secrets.
Example: Helping with AWS OIDC Setup
User: "How do I set up AWS OIDC credentials in ESC?"
1. Use the web-fetch tool to get AWS OIDC documentation from "https://www.pulumi.com/docs/esc/integrations/dynamic-login-credentials/aws-login/"
2. Provide the user with the configuration
3. Ask the user if they have a pre-defined role or need one created for them
4. Set up as much of the environment as possible, then guide them through any steps that you can't do for them
5. Help them test with `pulumi env get` or `pulumi env open` if necessaryCommon Workflows
Creating an Environment
pulumi env init my-org/my-project/dev-config
# Edit environment (accepts new definition from a file, better for agents, more difficult for users)
pulumi env edit --file /tmp/example.yml my-org/my-project/dev-configLinking to Stack
pulumi config env add my-project/dev-config
pulumi config # Verify environment values are accessibleAPI Access (Rare)
Always prefer CLI commands. Only use the API when absolutely necessary (e.g., bulk operations, automation).
Available API endpoints include:
GET /api/esc/environments/{orgName}- List environmentsGET /api/esc/environments/{orgName}/{projectName}/{envName}- Read environment definitionGET /api/esc/providers?orgName={orgName}- List available providers
Use the pulumi api CLI subcommand to make requests when needed, e.g. pulumi api /api/esc/providers -F orgName={orgName}.
Best Practices
Always use
fn::secretfor sensitive valuesPrefer OIDC over static keys
Use descriptive names like
<org>/my-app/production-awsnot<org>/app/prodLayer environments: base → cloud-provider → stack-specific
Verify that
pulumi configshows expected values after linking an environment to a stackPrefer using
pulumi env runfor commands needing environment variablesOnly use
pulumi env openwhen absolutely necessary, as it reveals secretsBefore using an existing environment, verify its account and role and get the user's confirmation; never select one by name alone. Never link an environment to a stack (
pulumi config env add) without explicit user confirmation, and never pass--yes.
Handling Credential Errors and Existing Environments
Credential errors
Start with the remediation in the error message. An expired or missing login usually just needs the user to re-authenticate, and most providers name the fix or the command:
AWS SSO:
Failed to refresh cached SSO credentials. Please refresh SSO login.→aws sso loginAWS temporary credentials:
ExpiredToken: The security token included in the request is expired→ refresh the session or keysAzure: re-run
az loginGCP: re-run
gcloud auth application-default loginPulumi Cloud (401 / unauthorized):
pulumi login
Relay the fix and have the user retry. If the error does not name a remediation
(for example a bare Unable to locate credentials, or an access-denied that may
mean the wrong account or profile rather than an expired login), don't guess —
identify how the project authenticates (provider config, the active profile, any
linked ESC environment) and address that.
Changing where the project gets its credentials (adding or switching an ESC environment, editing provider config) is a deliberate change, not a reflexive fix for an expired session. Do it only if the user wants it, and follow the rules below.
Never select an existing environment by name
Do not pick an environment because its name looks relevant (*-aws-oidc,
*-creds, *-workshop, etc.). A matching name does not mean it is the right
one or that it belongs to this user's work.
Before proposing any existing environment:
Inspect it with
pulumi env get <org>/<project>/<env>.Confirm the target it authenticates to matches where the user's resources actually live. An OIDC
roleArnnames a specific AWS account — if it points at a different account (a shared workshop, an instructor role, another team), it is the wrong environment and will run operations against the wrong account or fail.Show the candidate to the user and confirm it is theirs and correct before using it.
Linking an environment changes which credentials operations use — confirm first
pulumi config env add edits the stack config (Pulumi.<stack>.yaml) and
changes the credentials Pulumi operations run under. Never run it without
explicit user confirmation, and never pass --yes to skip that confirmation.
Tell the user what will change and let them decide.
Verify before claiming it worked
After linking, resolved credential values often show as [unknown] until the
environment is opened or run. Do not claim the error is fixed or that the next
operation will succeed until you have verified it — check pulumi config, and
confirm the credentials resolve to the expected account before declaring success.
Quick troubleshooting
"Environment not found": Check permissions with
pulumi env ls -o <org>"Secret decryption failed": Use
pulumi env opennotpulumi env get"Stack can't read values": Verify
pulumi config env lsto ensure the stack is listed.Ensure the environment is referenced only by the project-name/environment-name format.
Get the specific environment definition with
pulumi env get <org>/<project-name>/<environment-name>.Verify the
pulumiConfigkey exists and is nested under thevalueskey.
Files
- ATTRIBUTION.mdAdded by AutoGineer851 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md11.9 KiB
- agents/openai.yaml210 B
- use_cases.yaml1.3 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs network access
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Pulumi
- Publisher
- Pulumi (Official)
- Source
- pulumi/agent-skills · pulumi/skills/pulumi-esc · commit 82f222a
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Pulumi.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download pulumi-esc.zip