Provider Upgrade

---
name: provider-upgrade
description: >
  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. Applies to all
  providers (aws, azure-native, gcp, kubernetes, aws-native, cloudflare, datadog, etc.) — not
  just Tier 1. Do NOT use for querying which stacks use what package versions; use skill
  `package-usage` for cross-stack audits. Do NOT use for general infrastructure tasks.
---

# 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:… load the full skill through Skill Me