provider-resources

Create Terraform provider resources and data sources using the Plugin Framework.

Updated Jul 30, 2024
One-click install
npx skills add https://github.com/twidxuga/dotfiles --skill provider-resources-twidxuga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: provider-resources
Source: https://github.com/twidxuga/dotfiles/tree/main/opencode/dot-config/opencode/skills/terraform-provider-resources
Command: npx skills add https://github.com/twidxuga/dotfiles --skill provider-resources-twidxuga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement Terraform Provider resources and data sources using the Terraform Plugin Framework, standardizing CRUD operations, schema design, state management, and acceptance testing to reduce boilerplate and accelerate provider development.

Core Features & Use Cases

  • Resource & Data Source Scaffold: Provides patterns for creating resource and data source implementations, tests, and documentation.
  • CRUD, Schema, and State Management: Guides the full lifecycle, validation, and resource state handling with acceptance tests.
  • Provider Integration: Includes project structure and naming conventions to streamline integration with existing providers.

Quick Start

Create a new resource scaffold following the internal/service structure and register it with the provider.

Frequently Asked Questions about provider-resources

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

FAQPage Schema
How do I create Terraform provider resources using the Plugin Framework?

To create Terraform provider resources using the Plugin Framework, you need to implement resource scaffolding following the internal/service structure, define schemas, manage state, and register the new resource with the provider.

What is the standard project structure for Terraform Plugin Framework data sources?

The standard structure for Terraform Plugin Framework data sources involves organizing implementations and tests within an internal/service directory, applying specific naming conventions to streamline integration with existing provider codebases.

How do I implement CRUD operations and schema design for a Terraform provider?

Implementing CRUD operations and schema design for a Terraform provider requires using the Plugin Framework to guide the full lifecycle, handle resource state management, and apply validation rules for reliable provider development.

What's the best way to write acceptance tests for Terraform provider resources?

The best way to write acceptance tests for Terraform provider resources is to follow the standardized testing patterns provided by the Plugin Framework, ensuring reliable validation of CRUD operations and state handling.

Does this approach apply to both resources and data sources in Terraform provider development?

Yes, this approach applies to both resources and data sources in Terraform provider development, providing scaffold patterns for implementations, tests, and documentation to reduce boilerplate across the full lifecycle.