provider-upgrade SKILL.md skillA
provider-upgrade from pulumi/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pulumi/agent-skills/provider-upgrade@git:20261005.e2aa9b8Pins git:20261005.e2aa9b8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pulumi/agent-skills
- Path
pulumi/skills/provider-upgrade/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261005.e2aa9b8, committed Oct 5, 2026
- First version recorded
- Jun 2, 2026
- Size
- 15,686 bytes
- Repository stars
- 78
- License
- Apache-2.0
Upgrade any Pulumi provider to a newer version and reconcile the resulting diff. Use when users want to upgrade or update a provider (including editing package.json, requirements.txt, pyproject.toml, go.mod, or Pulumi.yaml to bump a provider SDK), check for breaking changes before or during an upgrade, fix resources that broke after a provider upgrade, or resolve unexpected replacements, creates, or deletes in a post-upgrade preview, including pulumi-gcp v10 errors such as a missing…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Upgrading Pulumi Providers ## The Principle A provider upgrade is a translation, not a change request. The user's infrastructure intent hasn't changed - they still want the same bucket, the same function, the same cluster. What changed is how the provider's API expresses that intent. Your job is to translate their existing code into the new API so that Pulumi sees no difference between what the code says and what already exists. There are four layers to keep in mind: 1. **User intent** - what the user wants in the cloud (unchanged during an upgrade) 2. **Code** - how the program expresses that intent using the provider API (may need updating) 3. **Pulumi state** - Pulumi's stored representation of what exists (may need reconciliation) 4. **Real cloud** - the actual infrastructure (should not change during an upgrade) During an upgrade, layers 2 and 3 may need to change so that they continue to correctly represent the unchanged layers 1 and 4. A correct translation produces zero diff. The Pulumi engine doesn't have a concept of "upgrade" - it just compares goal state (your code) against actual state (the state file) …
Read the whole file at its exact version.
How to install
mdr add pulumi/agent-skills/provider-upgrade@sha256:8bd6c5bfcb5f3428The line at the top of this page pins the label git:20261005.e2aa9b8, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_vlbh3qhlujiwwegb)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 2, 2026 and Oct 5, 2026, about one every 125 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261005.e2aa9b8 latest | 2026-10-05 | e2aa9b8 | 15,686 B | A | view · diff |
| git:20260602.8dccc43 | 2026-06-02 | 8dccc43 | 14,927 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15686 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
pulumi/agent-skills · 78 stars · license Apache-2.0 · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vlbh3qhlujiwwegb GET https://markdownregistry.com/api/v1/resolve?ref=pulumi/agent-skills/provider-upgrade GET https://markdownregistry.com/api/v1/blob/8bd6c5bfcb5f3428a91f8e107c8c2c736c0e0d20074d25037d2f9a48fbf5c47b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.