Provider Upgrade
This is for Pulumi users who need to bump a provider version without accidentally destroying infrastructure. The core insight is solid: an upgrade is a translation, not a change request. Your infrastructure intent hasn't changed, so a correct upgrade should produce zero diff. The skill walks you through the bump, preview, and diff checkpoint cycle, with clear categorization for every non-same resource. Category A is resources you touched (your translation is wrong if they don't show same). Category B is untouched resources (the provider version itself caused the diff). It covers the import-not-create pattern for newly explicit resources and the critical distinction between deleting from state versus actually destroying cloud infrastructure. Practical if you've ever stared at a post-upgrade preview wondering which diffs are safe.
- skills.sh installs
- 885
- GitHub stars
- 79
- last updated
- Aug 21, 2026
Install
$ npx -y skills add pulumi/agent-skills --skill provider-upgrade --agent claude-codeInstalls into .claude/skills of the current project.
Files
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:
- User intent - what the user wants in the cloud (unchanged during an upgrade)
- Code - how the program expresses that intent using the provider API (may need updating)
- Pulumi state - Pulumi's stored representation of what exists (may need reconciliation)
- 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.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageDetails
- Repository
- github.com/pulumi/agent-skills
- Categories
- DevOps & CI/CD, Git & Pull Requests, AI & Agent Building, Release Management, Debugging, Python, Cloud & Infrastructure
- First seen
- Jun 3, 2026
More from pulumi/agent-skills
All 12Recommended
More DevOps & CI/CD
geo-prospectzubair-trabzada/geo-seo-claudeCRM-lite for managing GEO agency prospects and clients. Track leads through the full sales pipeline: Lead → Qualified → Proposal Sent → Won → Lost. Store audit 881skills.sh installs
cold-emailalirezarezvani/claude-skillsWhen the user wants to write, improve, or build a sequence of B2B cold outreach emails to prospects who haven't asked to hear from them. Use when the user menti879skills.sh installs
clawsec-suiteprompt-security/clawsecClawSec suite manager with embedded advisory-feed monitoring, cryptographic signature verification, approval-gated malicious-skill response, and guided setup fo875skills.sh installs
sapui5-clisecondsky/sap-skillsManages SAPUI5/OpenUI5 projects using the UI5 Tooling CLI (@ui5/cli). Use when initializing UI5 projects, configuring ui5.yaml or ui5-workspace.yaml files, buil872skills.sh installs
ratatui-tuiblacktop/dotfilesBuild terminal UIs with ratatui following 2026 Rust best practices. Use when: (1) Creating new TUI apps, (2) Adding widgets/layouts, (3) Keyboard navigation/sta871skills.sh installs
shiny-bslibposit-dev/skillsBuild modern Shiny dashboards and applications using bslib (Bootstrap 5). Use when creating new Shiny apps, modernizing legacy apps (fluidPage, fluidRow/column,861skills.sh installs