pulumi-upgrade-provider

Automate Pulumi provider repository upgrades and resolve upgrade blockers.

1|Updated Apr 14, 2025

Search Tags:#git #dependency management #terraform #pulumi #provider upgrade

Ready to run

npx skills add https://github.com/mattwyskiel/dotfiles --skill pulumi-upgrade-provider

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pulumi-upgrade-provider
Source: https://github.com/mattwyskiel/dotfiles/tree/main/agents/.agents/skills/pulumi-upgrade-provider
Command: npx skills add https://github.com/mattwyskiel/dotfiles --skill pulumi-upgrade-provider

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires upgrade-provider, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of upgrading Pulumi provider repositories and resolves common issues that arise during the upgrade process.

Core Features & Use Cases

Automate Provider Upgrades: Automate the upgrade of Pulumi provider repositories to new upstream versions.
Handle Upgrade Blockers: Provide fixes for known issues like patch conflicts, missing module mappings, and vendored dependencies.
Use Case: When upgrading a Pulumi provider repository, this Skill can run the upgrade-provider tool, handle common errors, and guide the user through any manual interventions needed.

Quick Start

Use the pulumi-upgrade-provider skill to upgrade your Pulumi provider repository by running the command 'upgrade-pulumi-provider upgrade'.

Frequently Asked Questions about pulumi-upgrade-provider

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

FAQPage Schema

How do I automate upgrading a Pulumi provider repository?▼

Automate Pulumi provider upgrades by running the `upgrade-provider` tool to update repositories to new upstream versions while resolving common upgrade blockers like patch conflicts.

What issues commonly block Pulumi provider upgrades and how are they fixed?▼

Common Pulumi provider upgrade blockers include patch conflicts, missing module mappings, and vendored dependencies, which this Skill automatically detects and provides fixes for during the upgrade process.

Do I need Git to upgrade a Terraform provider using Pulumi?▼

Yes, upgrading Terraform providers with Pulumi requires Git operations and the `upgrade-provider` tool installed, as the automation manages repository updates and resolves patch conflicts locally.

Can I upgrade a Pulumi provider to a new upstream version without manual intervention?▼

Upgrading Pulumi providers is mostly automated, but manual intervention may be required for complex patch conflicts or missing module mappings that the automated upgrade-provider tool cannot resolve independently.

Why does my Pulumi provider upgrade fail with missing module mappings?▼

Pulumi provider upgrades fail with missing module mappings due to upstream changes, which this Skill identifies and guides you through resolving by updating the necessary module configurations.

What is the best way to handle vendored dependencies when upgrading Pulumi providers?▼

Handle vendored dependencies during Pulumi provider upgrades by using this Skill to detect dependency conflicts and apply targeted patches, ensuring the repository integrates upstream changes correctly.