tf-resource-migration

Name: tf-resource-migration
Availability: InStock
Author: Aiven

Migrate Terraform resources from legacy SDK provider to Plugin Framework.

132|78|Updated Feb 23, 2017

Search Tags:#terraform #migrate #code-generation #plugin-framework #sdkprovider #state-compatibility #yaml-definition

Ready to run

npx skills add https://github.com/aiven/terraform-provider-aiven --skill tf-resource-migration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tf-resource-migration
Source: https://github.com/aiven/terraform-provider-aiven/tree/main/tools/agents/skills/tf-resource-migration
Command: npx skills add https://github.com/aiven/terraform-provider-aiven --skill tf-resource-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate existing Terraform resources from the legacy SDK provider to the Plugin Framework while preserving state compatibility and behavior.

Core Features & Use Cases

Mapping schemas, IDs, and CRUD logic from internal/sdkprovider to internal/plugin, ensuring parity with the original SDK resource.
Providing YAML definitions, generation commands, and testing patterns to streamline the migration process.
Supporting state upgrade handling and backward-compatible behavior during transition.

Quick Start

Port a legacy aiven Terraform resource from the SDK to the Plugin Framework using the defined YAML workflow to maintain state compatibility and behavior parity.

Frequently Asked Questions about tf-resource-migration

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

FAQPage Schema

How do I migrate Terraform resources from the legacy SDK provider to the Plugin Framework?▼

Migrate Terraform resources from the legacy SDK provider to the Plugin Framework by mapping schemas, IDs, and CRUD logic from internal/sdkprovider to internal/plugin. This ensures behavior parity and preserves state compatibility during the transition using a YAML-based workflow.

How does state compatibility work when migrating Terraform SDK resources to the Plugin Framework?▼

State compatibility during Terraform SDK migration is maintained by preserving exact ID composition and handling state-upgrade considerations. This ensures the Plugin Framework resource matches the original implementation's schema and CRUD behavior without breaking existing deployments.

What is the best way to generate Plugin Framework code from legacy Terraform SDK resources?▼

Generate Plugin Framework code from legacy Terraform SDK resources using YAML-based definitions and specific generation commands. This approach streamlines the migration process while providing testing patterns to verify schema parity and backward-compatible behavior.

Can I maintain CRUD behavior parity when porting Terraform resources to the Plugin Framework?▼

Yes, you can maintain CRUD behavior parity when porting Terraform resources to the Plugin Framework by accurately mapping the logic from internal/sdkprovider to internal/plugin. This ensures the new resource implementation matches the original SDK behavior exactly.

What are the limitations of migrating Terraform resources to the Plugin Framework using YAML definitions?▼

Migrating Terraform resources to the Plugin Framework using YAML definitions requires exact ID composition and careful state-upgrade handling. Users must follow generation, testing, and backward-compatibility steps strictly to avoid breaking state parity with the original SDK implementation.