skills.rest
mattwyskiel
mattwyskielCOMMUNITY
Explore all skills by this author →
Website𝕏@MattWyskielGitHub

upstream-patches

Manage Terraform provider patch stacks via git submodules.

1|Updated Apr 14, 2025
Search Tags:#git#terraform#patch management#submodule#patching
One-click install
npx skills add https://github.com/mattwyskiel/dotfiles --skill upstream-patches
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upstream-patches
Source: https://github.com/mattwyskiel/dotfiles/tree/main/agents/.agents/skills/upstream-patches
Command: npx skills add https://github.com/mattwyskiel/dotfiles --skill upstream-patches

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the need for managing patches to Terraform provider submodules, enabling users to create, amend, remove, and rebase patches with ease.

Core Features & Use Cases

  • Patch Management: Automate the creation, amending, removal, and rebasing of Terraform provider patches.
  • Submodule Interaction: Works with a git submodule to apply and manage patches to the Terraform provider.
  • Use Case: When dealing with Terraform provider updates, this Skill can help you ensure that patches are applied correctly and that the provider continues to work as expected.

Quick Start

Run the ./scripts/upstream.sh init command to initialize the patch management process for your Terraform provider submodules.

Frequently Asked Questions about upstream-patches

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

FAQPage Schema
How do I manage Terraform provider patches applied to submodules?▼

Terraform provider patches applied to submodules are managed by creating, amending, removing, and rebasing patch stacks using git version control to ensure provider updates apply correctly.

What's the best way to rebase patches on a Terraform provider submodule?▼

Rebasing patches on a Terraform provider submodule is handled through dedicated patch management scripts that automate the stack rebasing process, ensuring updates do not conflict with existing modifications.

Do I need git to automate Terraform provider patch management?▼

Yes, git is required for Terraform provider patch management because the skill interacts with a git submodule to apply, amend, and rebase patches during provider updates.

How do I initialize a patch stack for my Terraform provider submodule?▼

To initialize a patch stack for a Terraform provider submodule, run the upstream.sh init script, which sets up the patch management process for applying and tracking submodule modifications.

When should I use a patch stack instead of directly modifying a Terraform provider submodule?▼

Use a patch stack when you need to maintain custom modifications to a Terraform provider submodule across upstream updates, allowing you to amend, remove, or rebase patches without losing changes.

Related Skills

Explore More Software Engineering Skills→
mattwyskielmattwyskiel
1

pulumi-upgrade-provider

Automate Pulumi provider repository upgrades and resolve upgrade blockers.

Community
Advanced
SnakeOSnakeO
9

debug:terraform

Diagnose Terraform state locks, provider authentication failures, drift, and module conflicts.

Community
Advanced
4lerman4lerman

senior-devops

Automates DevOps workflows including CI/CD pipelines, infrastructure as code, and container deployments with rollback support.

Community
Advanced
thrashr888thrashr888
4

version-upgrades

Automate Terraform CLI, provider, module, and policy version upgrades in HCP Terraform workspaces.

Community
Advanced