tf-resource-migration

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.

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.

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.

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.

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.