skills.rest
ConductorOne
ConductorOneOFFICIAL
Explore all skills by this author →
Website𝕏@ConductorOneIncGitHub

upgrading

Upgrade ConductorOne Terraform provider versions with breaking change and HCL migration handling.

6|4|Updated Jun 22, 2023
Search Tags:#infrastructure as code#breaking changes#terraform#provider upgrade#conductorone#hcl migration#terraform plan
One-click install
npx skills add https://github.com/ConductorOne/terraform-provider-conductorone --skill upgrading
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upgrading
Source: https://github.com/ConductorOne/terraform-provider-conductorone/tree/main/skills/upgrading
Command: npx skills add https://github.com/ConductorOne/terraform-provider-conductorone --skill upgrading

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about upgrading

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

FAQPage Schema
How do I safely upgrade the ConductorOne Terraform provider without state drift?▼

Safely upgrading the ConductorOne Terraform provider requires identifying breaking changes between your current and target versions, migrating affected HCL attributes, and validating the plan to prevent state drift and failed applies.

What breaking changes should I look for when updating my Terraform provider version?▼

When updating your Terraform provider, look for attribute renames, removed fields requiring migration to new resources, and known bugs like approval block plan drift or schema mismatches that block successful applies.

How do I migrate HCL attributes removed in newer ConductorOne Terraform provider releases?▼

Migrating removed HCL attributes involves using exact search patterns and rename instructions to update affected fields, and transitioning removed fields to their corresponding new resources to maintain configuration compatibility.

Does the ConductorOne Terraform provider upgrade process work with OpenTofu?▼

Yes, the upgrade process targets both Terraform and OpenTofu users managing ConductorOne resources, allowing you to navigate version ranges from v1.0.0 to current while handling broken releases and attribute migrations.

Why does my Terraform plan show approval block plan drift after a provider upgrade?▼

Approval block plan drift after a provider upgrade is a known bug; you resolve it by applying specific workarounds for schema mismatches and approval block drift to prevent unexpected resource recreation.

Which ConductorOne Terraform provider versions should I skip during an upgrade?▼

During a ConductorOne Terraform provider upgrade, you should skip broken releases like v1.1.0 and jump directly to stable target releases such as v1.3.0 to ensure a successful migration.

Related Skills

Explore More Software Engineering Skills→
thomast1906thomast1906
19

terraform-provider-upgrade

Automate Terraform provider upgrades with resource migration and state management.

Community
Advanced
camilooscargbaptistacamilooscargbaptista
7

terraform-iac

Audit Terraform configurations and modules for HCL codebase improvements.

Community
Advanced
bacocobacoco

terraform

Manage Terraform and OpenTofu infrastructure as code with HCL.

Community
Advanced
schovischovi
9

Release Notes Skill

Generate GitHub release notes for shelli releases using structured templates.

Community
Intermediate