azurerm-resource-implementation

Implement or modify Terraform AzureRM provider resources and data sources following Go SDK patterns.

6|7|Updated Oct 24, 2025

Search Tags:#code generation #azure #terraform #hashicorp #provider development #resource implementation

Ready to run

npx skills add https://github.com/WodansSon/terraform-azurerm-ai-assisted-development --skill azurerm-resource-implementation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: azurerm-resource-implementation
Source: https://github.com/WodansSon/terraform-azurerm-ai-assisted-development/tree/main/.github/skills/azurerm-resource-implementation
Command: npx skills add https://github.com/WodansSon/terraform-azurerm-ai-assisted-development --skill azurerm-resource-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of implementing and modifying resources and data sources within the Terraform AzureRM provider, ensuring adherence to established patterns and best practices.

Core Features & Use Cases

Resource Implementation: Generate new AzureRM resources or data sources following HashiCorp's Go SDK patterns.
Schema & Logic Updates: Modify existing resource schemas, validation rules, and CRUD operations.
Best Practice Adherence: Ensures consistency with provider standards for error handling, PATCH behavior, and testing.
Use Case: When adding a new Azure virtual machine resource to the provider, use this Skill to define its schema, implement the Create, Read, Update, and Delete functions, and ensure it follows the provider's established patterns for resource management.

Quick Start

Use the azurerm-resource-implementation skill to add a new Azure Key Vault resource to the provider.

Frequently Asked Questions about azurerm-resource-implementation

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

FAQPage Schema

How do I implement a new resource in the Terraform AzureRM provider?▼

Implementing a Terraform AzureRM provider resource involves defining its schema and CRUD functions following HashiCorp's Go SDK patterns. This process ensures typed SDK integration and proper resource management consistency.

What are the established patterns for AzureRM provider error formatting and PATCH behavior?▼

AzureRM provider error formatting and PATCH behavior follow established HashiCorp patterns to ensure consistent state management. Adhering to these standards prevents schema drift and maintains predictable CRUD operations.

Do I need to know Go and the HashiCorp SDK to modify AzureRM provider schemas?▼

Modifying AzureRM provider schemas requires knowledge of Go and the HashiCorp SDK. You need this foundation to correctly implement validation rules, update CRUD logic, and integrate typed SDK responses.

What is the best way to add validation rules to an existing Terraform AzureRM data source?▼

The best way to add validation rules to a Terraform AzureRM data source is by modifying the schema definition within the Go code. This ensures the new logic aligns with established provider development patterns and CRUD operations.

Can I use this approach to update CRUD logic for both AzureRM resources and data sources?▼

Yes, you can update CRUD logic for both AzureRM resources and data sources. Modifying these operations requires following established provider patterns for schema updates, error handling, and typed SDK integration.

Why does my custom AzureRM provider resource fail during state migration?▼

Custom AzureRM provider resources often fail during state migration if they do not follow established PATCH behavior and error formatting patterns. Ensuring schema consistency and proper CRUD logic implementation resolves these state conflicts.