provider-upgrade

Upgrade Pulumi provider versions while minimizing cloud state changes.

1|Updated Apr 14, 2025
One-click install
npx skills add https://github.com/mattwyskiel/dotfiles --skill provider-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: provider-upgrade
Source: https://github.com/mattwyskiel/dotfiles/tree/main/agents/.agents/skills/provider-upgrade
Command: npx skills add https://github.com/mattwyskiel/dotfiles --skill provider-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pulumi, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Manages provider upgrades for Pulumi infrastructure to ensure cloud resources are unchanged post-upgrade and to streamline the process of handling breaking changes.

Core Features & Use Cases

  • Version Management: Tracks provider version changes and upgrades.
  • Preview Diffs: Identifies and categorizes diffs during previews for quick assessment.
  • Fix Translation Issues: Directly addresses issues caused by API changes.
  • Manual Step Documentation: Provides guidelines for required manual interventions.
  • Use Cases: For any infrastructure stack that requires updating providers and for handling migration scenarios.

Quick Start

Upgrade the specified Pulumi provider in the current project using the provider-upgrade skill.

Frequently Asked Questions about provider-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade Pulumi provider versions without causing unintended cloud changes?

You can upgrade Pulumi provider versions safely by tracking version changes, categorizing preview diffs, and directly addressing API compatibility issues to ensure cloud resources remain unchanged post-upgrade. Required manual interventions are documented to mitigate deployment issues.

What is the best way to handle breaking changes when updating Pulumi providers?

The best way to handle breaking changes is by assessing categorized preview diffs and directly fixing translation issues caused by API changes. This minimizes cloud state changes and manages deployment issues through provider update handling and reconciliation processes.

How does Pulumi provider reconciliation work during an upgrade?

Pulumi provider reconciliation works by identifying and categorizing preview diffs during upgrades to assess cloud state changes. It directly addresses API compatibility issues and provides guidelines for manual interventions to ensure cloud resources remain unchanged post-upgrade.

Can I use this provider upgrade process across multiple Pulumi projects?

Yes, the provider upgrade process is applicable across Pulumi projects to manage version control and mitigate deployment issues. It streamlines provider upgrades by handling breaking changes and managing cloud state reconciliation for any infrastructure stack requiring updates.

Why does updating a Pulumi provider result in unexpected cloud state changes?

Unexpected cloud state changes during a Pulumi provider update occur due to API compatibility issues and breaking changes in the new version. The upgrade process mitigates this by categorizing preview diffs and fixing translation issues to minimize unintended cloud changes.

Do I need to manually fix translation issues after a Pulumi provider upgrade?

Yes, manual steps may be required after a Pulumi provider upgrade to address API changes that cannot be resolved automatically. The upgrade process documents guidelines for these required manual interventions to ensure cloud resources remain unchanged post-upgrade.