upgrading

What problem does it solve?

Upgrading the ConductorOne Terraform provider often introduces breaking changes, attribute renames, and known bugs that can cause state drift, failed applies, or unexpected resource recreation if handled manually. This Skill eliminates that risk by providing a structured, step-by-step upgrade workflow.

Core Features & Use Cases

• Breaking change identification: Guides users to locate all breaking changes between their current pinned provider version and target release, including notes on broken releases to skip.
• HCL migration support: Provides exact search patterns and rename instructions for affected attributes, plus guidance for migrating removed fields to new resources.
• Known issue workarounds: Includes fixes for common provider bugs like approval block plan drift and schema mismatches that would otherwise block successful upgrades.
• Use case example: A user upgrading from v1.0.x to v1.3.0 can use this Skill to avoid the broken v1.1.0 release, migrate the removed grant_policy_id field, and fix approval block drift without manual troubleshooting.

Quick Start

Use the upgrading skill to safely bump your pinned ConductorOne Terraform provider version to the latest stable release while handling all breaking changes and known issues.