provider-resources

To implement CRUD operations for a Terraform provider using the Plugin Framework, you must define resource schemas and manage state transitions within the Create, Read, Update, and Delete lifecycle methods. This process also involves handling errors and reporting diagnostics correctly during infrastructure deployments.

Designing schemas and managing state for Terraform custom resources requires defining attribute types within the Plugin Framework and mapping them to internal infrastructure components. Proper state management ensures configuration consistency and accurate resource tracking across deployments.

Writing acceptance tests for custom Terraform provider resources involves executing real infrastructure operations to verify CRUD behavior and state consistency. The Skill provides guidance on structuring these tests to ensure custom cloud services function correctly before documentation.

The Terraform Plugin Framework supports diagnostic reporting for resource development errors by allowing developers to attach detailed diagnostics to CRUD operations. This mechanism helps identify common error patterns and communicate infrastructure issues clearly during execution.

You should create a custom data source instead of a resource in Terraform provider development when you need to query and read existing infrastructure components without managing their lifecycle. Resources handle full CRUD operations, while data sources focus solely on reading state.

Documentation standards for Terraform provider resources require clear descriptions of schemas, arguments, and attributes for custom infrastructure components. Adhering to these standards ensures that users can correctly implement and reference the provider resources within their configurations.