INFRASTRUCTURE DEVELOPMENT / Pulumi
Debug a Failed Pulumi Operation
Reads the diagnostics Pulumi already recorded for a failed update or preview and places the fix in the program, state or environment.
“Debug a Pulumi update or preview that failed: read the failure Pulumi already recorded, find what caused it, and fix it. Load this skill when the user asks to debug, diagnose, or fix a failed update or preview, or points at a failing `pulumi up` or `pulumi preview`. Don't load it for authoring new infrastructure, migrations, or provider upgrades; those have their own skills. ”
01 / THE REASONING
Why this made the selection.
- It reads the recorded engine events with pulumi api instead of re-running the failed operation, and confirms the stack and version with the user before reading further.
- It reads every diagnostic, not only severity error, because a failed preview reports program errors as info#err stderr messages, per the file.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- pulumi/skills/pulumi-debug-failed-operation/SKILL.md (complete)
- README.md (skill groups, Claude Code plugin installation)
- LICENSE Apache-2.0 text
Our findings
- When the user names no operation, the skill walks back through updates until requestedBy.githubLogin matches pulumi whoami.
- Thin diagnostics send the agent to the log of whatever the resource shelled out to; missing access is reported as a blocker.
Not established by this review
- The installer was not run, and the skill was not executed against a project or service. No Pulumi stack was read.
- The agents/openai.yaml and use_cases.yaml files beside the skill were not opened.
- Not executed: it was not installed or run.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Add a skill to your workflow.
DOCUMENTED COMMAND
/plugin marketplace add pulumi/agent-skills Copying does not execute this command. It may retrieve a newer version than the reviewed source.
- The README then runs /plugin install pulumi, which bundles the authoring, migration and delegation skills, including this one.
- Neither command pins revision 2517e28e4bc029424e9c9ee48016394296be0f6a. Compare the installed SKILL.md with that revision or use the downloadable copy on this page.
- Log in with the Pulumi CLI yourself; the skill reads stack records through it.
Before you start
- Claude Code for the plugin path
- The Pulumi CLI logged in to Pulumi Cloud, and jq
THE COMPLETE REVIEWED DEFINITION
Read it before you reuse it.
Original source bytes, with attribution.
Review the host-specific setup notes above.
---
name: pulumi-debug-failed-operation
version: 1.1.1
description: |
Debug a Pulumi update or preview that failed: read the failure Pulumi already
recorded, find what caused it, and fix it. Load this skill when the user asks
to debug, diagnose, or fix a failed update or preview, or points at a failing
`pulumi up` or `pulumi preview`. Don't load it for authoring new
infrastructure, migrations, or provider upgrades; those have their own skills.
---
# Debug a failed Pulumi operation
A Pulumi operation has failed. Find what caused it and fix it. The user usually
points you at it, so start by working out which operation to debug, and confirm it
with the user before doing anything else. Pulumi recorded the error when the
operation failed, so once you know which operation it is you can read the error from
that record without running anything again.
The commands below reach Pulumi Cloud with `pulumi api`, a subcommand of the Pulumi
CLI that you run in your shell. Each one targets a stack by the explicit
`{orgName}/{projectName}/{stackName}` path you pass it, so you do not need that
stack selected locally to read its record. Selecting the stack matters later, when
you go to apply a fix.
## Start from the operation the user gave you
The user usually supplies the operation as a set of fields: the org, project, stack,
and update version (or preview id) — most often stated in prose, for example "debug
update 161 of vvm-dev". You need these to address the API: `{orgName}`,
`{projectName}`, `{stackName}`, and the version or preview id.
Fill any missing field from context. Take the org, project, or stack from the
currently selected stack (`pulumi stack --show-name`, `pulumi stack ls`) or
`Pulumi.yaml`. A missing version means the most recent update on that stack.
Briefly confirm which operation you landed on, its version or preview id and the
stack, before reading further. Keep it lightweight; they already told you.
## Read what failed
A failed update and a failed preview both record engine events, and the error is in
the diagnostic messages inside those events. Using the fields you settled on above,
fetch the events and pull the messages out.
For a failed update, use the `update` path with the version number:
```
pulumi api /api/stacks/{orgName}/{projectName}/{stackName}/update/<version>/events \
| jq -r '.events[].diagnosticEvent | select(. != null) | "[\(.severity)] \(.message)"' \
| sed 's/<{%reset%}>//g'
```
For a failed preview, use the `preview` path with the preview id:
```
pulumi api /api/stacks/{orgName}/{projectName}/{stackName}/preview/<preview-id>/events \
| jq -r '.events[].diagnosticEvent | select(. != null) | "[\(.severity)] \(.message)"' \
| sed 's/<{%reset%}>//g'
```
Read every message, not only the ones tagged `severity == "error"`. A provider
error carries that `error` tag, but a program error, which is the common case when
a preview fails, arrives as a stderr diagnostic tagged `info#err`. The trailing
`sed` strips terminal color codes that Pulumi embeds in the text, which otherwise
show up as `<{%reset%}>`.
## Find the cause and where the fix belongs
An operation can fail with errors from more than one resource, so read all of the
diagnostics first, then work through each error. Trace every error back to the
resource that raised it (its URN and type), to where that resource is declared in
the program, and to the inputs that feed it.
The error text tells you what kind of problem it is, and that points to where the
fix belongs. A Pulumi fix lands in one of three places, and naming the right one
keeps you from editing code that was never the problem.
- **The program.** The code is wrong: a bad reference, a wrong type, an input the
provider rejected, or a value used before it had resolved. This is what a failed
preview usually reports, because the plan could not be built. Fix it by editing
the code.
- **The state.** The code is correct, but the stored state and the real cloud
resources disagree. Reconcile drift with `pulumi refresh`, and bring a resource
that already exists outside the state under management with `pulumi import`
rather than recreating it. Note that an operation which failed partway through
applying may have already changed some resources, so check the current state
before you decide.
- **The environment.** The problem is outside Pulumi: credentials, permissions,
OIDC, or a quota. Fix the role, the ESC environment, or the capacity that the
provider rejected, rather than the resource code.
When a diagnostic is empty or too thin to act on, the real error usually isn't in
the record — it's in the log of whatever the resource shelled out to. Read it
there. If reaching it needs access you don't have (a token, a run, a not-found),
stop and tell the user what you're blocked on and the one thing you need from them.
## Fix the cause
Make the smallest change that addresses the root cause. How you confirm the fix,
and how you deliver it, whether as a local edit or as a pull request, follow your
mode's workflow, not this skill.
## If the user didn't say which operation
When the user gives you nothing to go on, debug their most recent operation on the
stack. The update list does not record who ran each update, so find it through the
API:
1. Run `pulumi whoami` to get the current user's login.
2. Read the latest update and who requested it with
`pulumi api /api/stacks/{orgName}/{projectName}/{stackName}/updates/latest`, and
compare its `requestedBy.githubLogin` to the login from step 1.
3. If they match, that update is the one to debug. If they do not, walk back one
version at a time with
`pulumi api /api/stacks/{orgName}/{projectName}/{stackName}/updates/<n>` until
`requestedBy.githubLogin` matches the user.
Tell the user which operation you landed on, its version, kind, and result, and
confirm it is the one they mean before going further.
The download contains SKILL.md. Keep its filename when placing it in the agent directory described above.
By Pulumi. Exact upstream source ↗ · Licence · Attribution
SHA-256 7a83abe3d985041e07ec1220c375376ebe9c6a140917a9565c38f0d9db72f034
Read the applicable licence
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.
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Skill definition ↗Checked
https://github.com/pulumi/agent-skills/blob/2517e28e4bc029424e9c9ee48016394296be0f6a/pulumi/skills/pulumi-debug-failed-operation/SKILL.md
Supports: summary, upstreamDescription, whySelected, limitations, access, review
https://github.com/pulumi/agent-skills/blob/2517e28e4bc029424e9c9ee48016394296be0f6a/README.md
Supports: install, compatibility
- Repository licence ↗Checked
https://github.com/pulumi/agent-skills/blob/2517e28e4bc029424e9c9ee48016394296be0f6a/LICENSE
Supports: license
https://raw.githubusercontent.com/pulumi/agent-skills/2517e28e4bc029424e9c9ee48016394296be0f6a/pulumi/skills/pulumi-debug-failed-operation/SKILL.md
Supports: upstreamDescription, bestFor, review.notTested, review.reviewedAt