Terraform provider resources

Guides writing Terraform provider resources and data sources on the Plugin Framework: schema, CRUD, not-found handling, import, waiters for eventually consistent APIs and minimum tests. Use when adding, changing or reviewing a provider resource.

CodingPack: HashiCorp skillslinkprovider-resources
Author
Source
hashicorp/agent-skills/plugins/terraform/skills/provider-resources @ 5e30fa5
License
MPL-2.0

About this skill

What it does

The skill guides the agent through writing resources and data sources for a Terraform provider in Go. New code goes on the Plugin Framework only; SDKv2 is for maintaining existing resources, and go.mod shows which one a provider uses. Its resource template covers the client wiring in Configure, a schema with plan modifiers (RequiresReplace, UseStateForUnknown) and validators, and CRUD with fixed behaviour: Read drops the resource from state when the API says it is gone, Update calls the API only for changed attributes, Delete treats "already deleted" as success, Import passes the ID through. A shared finder keeps not-found handling identical everywhere. It also rules out a redundant id, wants docs generated by tfplugindocs and ends with a pre-submission checklist.

references/design-principles.md covers what should be a resource: the smallest object with its own CRUD, one API per resource, singular versus plural data sources. references/retries-and-waiters.md sorts eventual-consistency failures into three classes, each with its own fix: a short not-found retry right after create, a bounded retry on one typed error, and a status-plus-wait pair built on retry.StateChangeConf.

When to use it, and when not

Use it when adding or changing a resource or data source, deciding how to model an API object, or reviewing a resource before a pull request.

It is not for HCL that uses a provider. SDKv2 migration, the provider's own Configure, docs and running acceptance tests belong to other skills in HashiCorp's plugin (provider-framework-migration, provider-configuration, provider-docs, run-acceptance-tests) that our catalog does not list.

How to run it

We do not copy this skill: its files are under MPL-2.0, a file-level copyleft licence outside the set we copy under. Install it from HashiCorp's repository with the button to the source: one skill via npx skills add hashicorp/agent-skills/plugins/terraform/skills/provider-resources, or the whole terraform plugin, which brings those skills too, via claude plugin marketplace add hashicorp/agent-skills, then claude plugin install terraform@hashicorp. In Codex: codex plugin marketplace add hashicorp/agent-skills, then install terraform from /plugins and start a new session. In Claude Code, the plugin's skill may appear as /terraform:provider-resources.

  • Claude Code: /provider-resources, or ask for the skill by name.
  • Codex: $provider-resources.
  • Cursor: type / in the Agent chat and pick provider-resources.

Example: /provider-resources Add an examplecloud_widget resource with import and a waiter from CREATING to ACTIVE.

How it differs from similar skills

Terraform provider test patterns is its testing half: this skill names the minimum tests (_basic with an import step, _disappears, one per attribute), then defers to that skill for state checks, plan checks, sweepers and ephemeral resources. Nothing else in the catalog covers writing Terraform providers.

Install

This skill is not copied to the catalog: its licence allows a copy only under the same licence, and the catalog does not copy under such licences. Install it from the author's repository.

Open the source

Connect through AnyModel API

This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.

More from the pack HashiCorp skills

Terraform style guide

Applies HashiCorp's Terraform style conventions: standard file split, formatting, naming, typed variables, for_each over count, pinned versions and secrets kept out of state. Use when writing, reviewing or generating Terraform HCL.

Terraform tests

Writes and runs Terraform's native tests in .tftest.hcl files: run blocks, assertions, plan and apply modes, expect_failures, mock providers and CI pipelines. Use when adding tests to a Terraform module or fixing a failing terraform test.

Terraform Stacks

Writes Terraform Stacks configurations for HCP Terraform: components in .tfcomponent.hcl, deployments in .tfdeploy.hcl, OIDC identity tokens, auto-approve rules, linked Stacks and API monitoring. Use when building or debugging a Stack.

Refactor Terraform into modules

Splits a monolithic Terraform configuration into a reusable module with a typed interface, then migrates state with moved blocks or terraform state mv so nothing is recreated. Use when a root config has grown too large or repeats itself.

Terraform search and import

Finds existing cloud resources with Terraform Search queries in .tfquery.hcl, generates resource and import blocks, and falls back to manual import for unsupported types. Use when bringing hand-made infrastructure under Terraform.

Terraform policy files

Writes, converts and tests HCP Terraform policy files (.policy.hcl, .policytest.hcl), including Sentinel-to-tfpolicy conversion with a quality label per policy. Use when writing a new policy, porting Sentinel or debugging a policy test.

Azure Verified Modules for Terraform

Applies the 37 Azure Verified Modules requirements to Terraform modules: provider versions, sources, naming, variables, outputs, breaking changes and repository rules. Use when writing or reviewing an Azure module meant for AVM certification.

Terraform provider test patterns

Covers acceptance tests for Terraform providers with terraform-plugin-testing: test steps, state and plan checks, import, disappears and regression tests, sweepers and ephemeral resources. Use when writing, reviewing or debugging provider acceptance tests.

AWS AMIs with Packer

Builds Amazon Machine Images with Packer's amazon-ebs builder from a ready HCL template, with source filters, multi-region copies, credentials and fixes for common build errors. Use when creating a custom AMI for EC2.