---
title: "Terraform Provider Resources: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/skills/hashicorp-provider-resources/
description: "Implements Plugin Framework resources and data sources, including drift, import and the acceptance tests a submission needs."
---

# Terraform Provider Resources: review, setup & limitations · Undominated.ai

> Implements Plugin Framework resources and data sources, including drift, import and the acceptance tests a submission needs.

[← Explore all skills](/skills/)

INFRASTRUCTURE DEVELOPMENT / HashiCorp

# Terraform Provider Resources

Implements Plugin Framework resources and data sources, including drift, import and the acceptance tests a submission needs.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/hashicorp/agent-skills/tree/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/provider-resources)

SOURCE REVIEW

 Reviewed 2026-10-15
 Evidence 4 linked sources
 Publisher HashiCorp
 Licence [MPL-2.0 ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/LICENSE)
 Revision f706481af9b8
 [Read what was—and wasn’t—checked ↓](#review)

“Implement Terraform Provider resources and data sources using the Plugin Framework: CRUD operations, schema design, plan modifiers and validators, not-found handling, waiters for eventually consistent APIs, import support, resource design principles, and required acceptance test coverage. Use when adding or changing a resource or data source, deciding whether an API concept should be a resource, wiring a resource to the provider's configured client, handling drift or resource-not-found, or reviewing a resource implementation before submission.”

 [HashiCorp · upstream description ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/provider-resources/SKILL.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - The scope names CRUD, plan modifiers, validators, waiters, import and acceptance-test coverage as one workflow.
- It includes the decision of whether an API concept should be a resource at all.

### A good fit for

 - Adding a Plugin Framework resource
- Reviewing a provider resource before submission
- Implement drift-aware Read/Delete behavior and eventual-consistency waiters.
- Choose lookup cardinality and empty-result behavior when designing a provider data source.

### Weigh up before choosing

 - MPL-2.0 is file-level copyleft for modified redistributions of this file.
- Acceptance-test commands are not a substitute for running them against the target API.
- Framework code still must preserve the target API semantics; read-only data sources must not perform writes.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - plugins/terraform/skills/provider-resources/SKILL.md
- README.md
- LICENSE
- vercel-labs/skills@48dc9e8eb8aa19040e91cb90ba0b642c9cbad57e:README.md
- SKILLS.md

### Our findings

 - Frontmatter licence is MPL-2.0 and lifecycle-status is active.
- The description requires acceptance-test coverage, not only a schema.
- Read removes externally deleted objects from state; Delete treats already-gone as the desired result.
- The definition distinguishes singular lookup errors from plural zero-or-more collection results.
- Read must remove the resource from state when it was deleted outside Terraform.
- The design rules give singular and plural data sources different match semantics: singular lookups error on no or multiple matches, while plural lookups return a collection including empty results.

### Not established by this review

 - The skill was not executed inside a host agent.
- No bundled script, if present, was run against a real project.
- Not executed: it was not installed or run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Add a skill to your workflow.

[Upstream setup instructions ↗](https://github.com/vercel-labs/skills/blob/48dc9e8eb8aa19040e91cb90ba0b642c9cbad57e/README.md)

DOCUMENTED COMMAND

 npx skills add hashicorp/agent-skills/plugins/terraform/skills/provider-resources --skill provider-resources Copy command ↗

Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.

 Optional: install the reviewed revision

Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.

 npx skills@1.7.1 add https://github.com/hashicorp/agent-skills/tree/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/provider-resources --skill provider-resources Copy reviewed-revision command ↗ - The command pins the reviewed tree and Skills CLI 1.7.1 (vercel-labs/skills package.json at 48dc9e8e). The publisher documents npx skills add hashicorp/agent-skills/<installation-path> in SKILLS.md, which follows the default branch.
- Retain all supporting files; separately configure companion skills, runtimes and service credentials named in the definition.
- Review the resulting diff and use an isolated target before any migration, deployment, load test or warehouse operation.
- For manual installation instead, download the complete bundle from https://undominated.ai/resources/skills/hashicorp-provider-resources/bundle.zip and extract it into a new directory. It holds SKILL.md and 2 supporting files unchanged at revision f706481a, the upstream licence and an attribution file.
- Place the extracted directory in your host's documented skills directory, named provider-resources. Keep SKILL.md and the licence together.

### Before you start

 - Go, Terraform, the matching provider SDK, and an isolated account for any acceptance tests.

### Compatibility

Agent Skills-compatible hosts · Terraform Plugin Framework

### Local Markdown instructions

 - Read the installed skill files
- No network call is made by the catalogue record itself
- CRUD and disappears tests create/delete real API objects; scope credentials to test resources.

### Cost model

Source is free to read under the stated licence. A host agent or model provider may charge for use.

THE COMPLETE REVIEWED DEFINITION

## Read it before you reuse it.

Original source bytes, with attribution. Review the host-specific setup notes above.

 Copy definition ↗ [Download complete resource + licence ↗](/resources/skills/hashicorp-provider-resources/bundle.zip)[Raw Markdown ↗](/resources/skills/hashicorp-provider-resources/definition.md)
 ---
name: provider-resources
description: >-
 Implement Terraform Provider resources and data sources using the Plugin
 Framework: CRUD operations, schema design, plan modifiers and validators,
 not-found handling, waiters for eventually consistent APIs, import support,
 resource design principles, and required acceptance test coverage. Use when
 adding or changing a resource or data source, deciding whether an API
 concept should be a resource, wiring a resource to the provider's
 configured client, handling drift or resource-not-found, or reviewing a
 resource implementation before submission.
license: MPL-2.0
metadata:
 lifecycle-status: active
 copyright: Copyright IBM Corp. 2026
 version: "0.0.1"
---

# Terraform Provider Resources Implementation Guide

## Overview

This guide covers developing Terraform Provider resources and data sources.
Resources represent infrastructure objects that Terraform manages through
Create, Read, Update, and Delete (CRUD) operations.

**Use the [Plugin Framework](https://developer.hashicorp.com/terraform/plugin/framework)
for all net-new resources and data sources.** Plugin SDKv2 is for maintaining
resources that already exist on it; do not write new code against it. A
provider can serve both during migration by muxing
([terraform-plugin-mux](https://developer.hashicorp.com/terraform/plugin/mux)),
so adopting the Framework never requires a big-bang rewrite. To tell which
mode an existing provider is in, check `go.mod`: `terraform-plugin-mux`
present means it serves both SDKv2 and Framework code; only
`terraform-plugin-sdk/v2` means SDKv2-only; only
`terraform-plugin-framework` means Framework-only. Be cautious about
*migrating* existing SDKv2 resources: the Framework distinguishes null from
zero values, so naive migrations change behavior for existing users (use the
`provider-framework-migration` skill, if available).

**References** (load when needed):
- `references/design-principles.md` — what should (and should not) become a
 resource; data source semantics; relationship and async-task modeling
- `references/retries-and-waiters.md` — eventual consistency, retry
 patterns, and status/wait function structure

## File Structure

Most providers keep every resource in a single package:

```
internal/provider/
├── provider.go # Provider schema + Configure
├── widget_resource.go # Resource implementation
├── widget_resource_test.go # Acceptance tests
├── widget_data_source.go # Data source (if applicable)
└── widget_data_source_test.go
```

Large multi-service providers (e.g. terraform-provider-aws) split into
`internal/service/<service>/` packages instead, with an idiomatic file
taxonomy worth adopting once a package grows: `consts.go`, `find.go`
(finders), `status.go` (status functions), `wait.go` (waiters), `sweep.go`
(test sweepers), `exports_test.go`.

Documentation lives in `docs/` and is generated with `tfplugindocs`:

```
docs/
├── resources/<name>.md # generated; optional <name>.md.tmpl template
└── data-sources/<name>.md
```

(Hand-written `website/docs/r/*.html.markdown` trees exist in some older,
large providers — follow the target repo's convention when editing one.)

## Resource Structure

A Framework resource is a struct holding the API client, with interface
assertions making the implemented behaviors explicit:

```go
var (
 _ resource.Resource = &widgetResource{}
 _ resource.ResourceWithConfigure = &widgetResource{}
 _ resource.ResourceWithImportState = &widgetResource{}
)

func NewWidgetResource() resource.Resource {
 return &widgetResource{}
}

type widgetResource struct {
 client *examplecloud.Client
}

func (r *widgetResource) Metadata(_ context.Context, req resource.MetadataRequest, resp *resource.MetadataResponse) {
 resp.TypeName = req.ProviderTypeName + "_widget"
}

// Configure receives the client the provider built in its own Configure.
func (r *widgetResource) Configure(_ context.Context, req resource.ConfigureRequest, resp *resource.ConfigureResponse) {
 if req.ProviderData == nil {
 return // provider not yet configured (e.g. validation phase)
 }
 client, ok := req.ProviderData.(*examplecloud.Client)
 if !ok {
 resp.Diagnostics.AddError(
 "Unexpected Resource Configure Type",
 fmt.Sprintf("Expected *examplecloud.Client, got: %T.", req.ProviderData),
 )
 return
 }
 r.client = client
}

func (r *widgetResource) Schema(ctx context.Context, req resource.SchemaRequest, resp *resource.SchemaResponse) {
 resp.Schema = schema.Schema{
 Attributes: map[string]schema.Attribute{
 "name": schema.StringAttribute{
 Required: true,
 PlanModifiers: []planmodifier.String{
 stringplanmodifier.RequiresReplace(),
 },
 Validators: []validator.String{
 stringvalidator.LengthBetween(1, 255),
 },
 },
 "id": schema.StringAttribute{
 Computed: true,
 PlanModifiers: []planmodifier.String{
 stringplanmodifier.UseStateForUnknown(),
 },
 },
 },
 }
}
```

How the provider's `Configure` produces that client — schema, credential
resolution, validation — is covered by the `provider-configuration` skill
(if available).

**On `id`:** SDKv2 required a magic `id` attribute; the Framework does not.
If the API has its own identifier, expose it under its real meaning and do
not add a second, redundant `id`. Only keep `id` when it *is* the API's
identifier (as above).

## CRUD Operations

### Create

```go
func (r *widgetResource) Create(ctx context.Context, req resource.CreateRequest, resp *resource.CreateResponse) {
 var data widgetResourceModel
 resp.Diagnostics.Append(req.Plan.Get(ctx, &data)...)
 if resp.Diagnostics.HasError() {
 return
 }

 input := &examplecloud.CreateWidgetInput{
 Name: data.Name.ValueStringPointer(),
 }

 output, err := r.client.CreateWidget(ctx, input)
 if err != nil {
 resp.Diagnostics.AddError(
 "Error creating Widget",
 fmt.Sprintf("creating Widget (%s): %s", data.Name.ValueString(), err),
 )
 return
 }

 data.ID = types.StringPointerValue(output.ID)

 // For eventually consistent APIs, wait for the resource to be usable
 // before returning — see references/retries-and-waiters.md.

 resp.Diagnostics.Append(resp.State.Set(ctx, &data)...)
}
```

### Read

Read must handle out-of-band deletion by removing the resource from state so
the next plan recreates it, rather than erroring forever:

```go
func (r *widgetResource) Read(ctx context.Context, req resource.ReadRequest, resp *resource.ReadResponse) {
 var data widgetResourceModel
 resp.Diagnostics.Append(req.State.Get(ctx, &data)...)
 if resp.Diagnostics.HasError() {
 return
 }

 output, err := findWidgetByID(ctx, r.client, data.ID.ValueString())
 if isNotFound(err) {
 tflog.Warn(ctx, "Widget not found, removing from state", map[string]any{"id": data.ID.ValueString()})
 resp.State.RemoveResource(ctx)
 return
 }
 if err != nil {
 resp.Diagnostics.AddError(
 "Error reading Widget",
 fmt.Sprintf("reading Widget (%s): %s", data.ID.ValueString(), err),
 )
 return
 }

 data.Name = types.StringPointerValue(output.Name)

 resp.Diagnostics.Append(resp.State.Set(ctx, &data)...)
}
```

### Update

Only call the API for attributes that actually changed; compare plan against
state:

```go
func (r *widgetResource) Update(ctx context.Context, req resource.UpdateRequest, resp *resource.UpdateResponse) {
 var plan, state widgetResourceModel
 resp.Diagnostics.Append(req.Plan.Get(ctx, &plan)...)
 resp.Diagnostics.Append(req.State.Get(ctx, &state)...)
 if resp.Diagnostics.HasError() {
 return
 }

 if !plan.Description.Equal(state.Description) {
 input := &examplecloud.UpdateWidgetInput{
 ID: plan.ID.ValueStringPointer(),
 Description: plan.Description.ValueStringPointer(),
 }
 if _, err := r.client.UpdateWidget(ctx, input); err != nil {
 resp.Diagnostics.AddError(
 "Error updating Widget",
 fmt.Sprintf("updating Widget (%s): %s", plan.ID.ValueString(), err),
 )
 return
 }
 }

 resp.Diagnostics.Append(resp.State.Set(ctx, &plan)...)
}
```

### Delete

Treat "already gone" as success — the desired end state is reached:

```go
func (r *widgetResource) Delete(ctx context.Context, req resource.DeleteRequest, resp *resource.DeleteResponse) {
 var data widgetResourceModel
 resp.Diagnostics.Append(req.State.Get(ctx, &data)...)
 if resp.Diagnostics.HasError() {
 return
 }

 _, err := r.client.DeleteWidget(ctx, &examplecloud.DeleteWidgetInput{
 ID: data.ID.ValueStringPointer(),
 })
 if isNotFound(err) {
 return
 }
 if err != nil {
 resp.Diagnostics.AddError(
 "Error deleting Widget",
 fmt.Sprintf("deleting Widget (%s): %s", data.ID.ValueString(), err),
 )
 return
 }
}
```

### Import

With `ResourceWithImportState` asserted, passthrough of the identifier is
one line:

```go
func (r *widgetResource) ImportState(ctx context.Context, req resource.ImportStateRequest, resp *resource.ImportStateResponse) {
 resource.ImportStatePassthroughID(ctx, path.Root("id"), req, resp)
}
```

For multi-part identifiers, parse a delimited import ID (commonly
comma-separated) and set each attribute explicitly.

## Resource Design Principles

Before implementing, check the shape of the thing being modeled (full
treatment in `references/design-principles.md`):

- A resource is the *smallest* useful building block; if the API offers
 CRUD for it, it likely deserves its own resource.
- A resource should talk to **one** API/service only — cross-service
 resources break permissions, auditing, and endpoint configuration.
- Data sources are read-only and side-effect free. A *singular* data source
 errors on zero or multiple matches; a *plural* data source (plural noun
 name) returns zero-or-more as a collection and errors on neither.
- Attached policies/rules, long-running task invocations, and versioned
 artifacts usually deserve their *own* resources rather than attributes on
 the parent.
- Start/stop or enable/disable state belongs as an attribute *in* the
 resource, not as a separate resource.

## Schema Design

### Attribute Types

| Terraform Type | Framework Type | Use Case |
|----------------|----------------|----------|
| `string` | `schema.StringAttribute` | Names, identifiers |
| `number` | `schema.Int64Attribute`, `schema.Float64Attribute` | Counts, sizes |
| `bool` | `schema.BoolAttribute` | Feature flags |
| `list` | `schema.ListAttribute` | Ordered collections |
| `set` | `schema.SetAttribute` | Unordered unique items |
| `map` | `schema.MapAttribute` | Key-value pairs |
| `object` | `schema.SingleNestedAttribute` | Complex nested config |

Give every attribute a `MarkdownDescription` — `tfplugindocs` publishes it,
and it is the primary user-facing documentation.

### Plan Modifiers

```go
// Force replacement when value changes
stringplanmodifier.RequiresReplace()

// Keep a known value during plan instead of (known after apply)
stringplanmodifier.UseStateForUnknown()
```

### Validators

```go
stringvalidator.LengthBetween(1, 255)
stringvalidator.RegexMatches(regexp.MustCompile(`^[a-z0-9-]+$`), "must be lowercase alphanumeric with hyphens")
stringvalidator.OneOf("small", "medium", "large")
int64validator.Between(1, 100)
listvalidator.SizeAtLeast(1)
```

### Sensitive Attributes

```go
"password": schema.StringAttribute{
 Required: true,
 Sensitive: true,
},
```

## State Management

### Finders

Centralize "get one thing or a typed not-found" in a finder so Read, Delete,
waiters, and tests all share identical not-found semantics:

```go
func findWidgetByID(ctx context.Context, client *examplecloud.Client, id string) (*examplecloud.Widget, error) {
 output, err := client.GetWidget(ctx, &examplecloud.GetWidgetInput{ID: &id})
 if err != nil {
 var apiErr *examplecloud.NotFoundError
 if errors.As(err, &apiErr) {
 return nil, &retry.NotFoundError{LastError: err}
 }
 return nil, fmt.Errorf("getting Widget (%s): %w", id, err)
 }
 if output == nil || output.Widget == nil {
 return nil, &retry.NotFoundError{Message: "empty result"}
 }
 return output.Widget, nil
}

func isNotFound(err error) bool {
 var nfe *retry.NotFoundError
 return errors.As(err, &nfe)
}
```

### Waiting for Resource States

Many APIs return from Create/Delete before the resource is usable/gone. Use
`retry.StateChangeConf` (from
`github.com/hashicorp/terraform-plugin-sdk/v2/helper/retry` — usable from
Framework providers), with a status function built on the finder and
timeouts in named constants:

```go
stateConf := &retry.StateChangeConf{
 Pending: []string{"CREATING", "PENDING"},
 Target: []string{"ACTIVE"},
 Refresh: statusWidget(ctx, r.client, id), // one poll of the finder: (obj, status, err)
 Timeout: widgetCreatedTimeout,
}
outputRaw, err := stateConf.WaitForStateContext(ctx)
```

The full status/wait function pairs (create and delete waiters, failure-state
handling, post-create not-found retries, eventual-consistency patterns) are
in `references/retries-and-waiters.md` — read it whenever the API is
asynchronous or eventually consistent.

## Testing

Every resource ships with, at minimum:

- **`_basic`** — create with minimal config, assert attributes, then an
 import step (`ImportState: true`, `ImportStateVerify: true`)
- **`_disappears`** — delete the object out-of-band mid-test; the next plan
 must propose recreation, not error
- **Per-attribute tests** — exercise updates for each non-trivial argument

Naming grammar: tests `TestAcc{Resource}_{group?}_{description}`, helpers
`testAccCheck{Resource}Exists` / `testAccCheck{Resource}Destroy`, config
functions `testAcc{Resource}Config_{description}`. Keep configs
self-contained, randomize real resource names, and never hardcode
environment-specific values (account IDs, zones, versions).

```go
func TestAccWidget_basic(t *testing.T) {
 rName := acctest.RandStringFromCharSet(10, acctest.CharSetAlphaNum)
 resourceName := "examplecloud_widget.test"

 resource.ParallelTest(t, resource.TestCase{
 PreCheck: func() { testAccPreCheck(t) },
 ProtoV6ProviderFactories: testAccProtoV6ProviderFactories,
 CheckDestroy: testAccCheckWidgetDestroy,
 Steps: []resource.TestStep{
 {
 Config: testAccWidgetConfig_basic(rName),
 ConfigStateChecks: []statecheck.StateCheck{
 statecheck.ExpectKnownValue(resourceName, tfjsonpath.New("name"), knownvalue.StringExact(rName)),
 statecheck.ExpectKnownValue(resourceName, tfjsonpath.New("id"), knownvalue.NotNull()),
 },
 },
 {
 ResourceName: resourceName,
 ImportState: true,
 ImportStateVerify: true,
 },
 },
 })
}

func testAccWidgetConfig_basic(rName string) string {
 return fmt.Sprintf(`
resource "examplecloud_widget" "test" {
 name = %[1]q
}
`, rName)
}
```

Use the `provider-test-patterns` skill (if available) for the full testing
treatment: config helper style (`%[1]q` indexed verbs), statecheck/plancheck,
CompareValue, custom StateCheck implementations for exists/disappears
helpers, sweepers, and ephemeral resource testing. Use the
`run-acceptance-tests` skill for executing and debugging test runs.

## Error Handling

Match API errors by type, not message text, and wrap with context:

```go
var notFound *examplecloud.NotFoundError
if errors.As(err, &notFound) {
 // resource doesn't exist
}

// Wrapping inside helpers: preserve the cause with %w
return fmt.Errorf("creating Widget (%s): %w", name, err)
```

Diagnostics follow a consistent grammar — summary names the operation and
type, detail carries identifier and cause:

```go
resp.Diagnostics.AddError(
 "Error creating Widget",
 fmt.Sprintf("creating Widget (%s): %s", name, err),
)

resp.Diagnostics.AddAttributeError(
 path.Root("name"),
 "Invalid name",
 "Name must be lowercase alphanumeric",
)
```

## Documentation

Write attribute `MarkdownDescription`s first — they are the source of
truth. Then generate Registry documentation with `tfplugindocs`
(`go generate ./...` where wired up), adding `docs/**/*.md.tmpl` templates
only for prose and examples the generator cannot derive. Use the
`provider-docs` skill (if available) for the full documentation workflow and
Registry publication rules.

## Pre-Submission Checklist

- [ ] Plugin Framework used (no new SDKv2 code)
- [ ] Resource has all CRUD operations implemented
- [ ] Read removes missing resources from state; Delete tolerates already-deleted
- [ ] No redundant `id` attribute (real API identifier exposed instead)
- [ ] Import implemented and covered by an `ImportStateVerify` step
- [ ] `_basic`, `_disappears`, and per-attribute tests present
- [ ] Waiters used where the API is eventually consistent
- [ ] Error messages name the operation, type, and identifier
- [ ] Sensitive attributes marked; every attribute has a description
- [ ] Docs generated with `tfplugindocs`
- [ ] Changelog entry added, if the repo tracks release notes (check CONTRIBUTING)

## References

- [Terraform Plugin Framework](https://developer.hashicorp.com/terraform/plugin/framework)
- [Resource Development](https://developer.hashicorp.com/terraform/plugin/framework/resources)
- [Data Source Development](https://developer.hashicorp.com/terraform/plugin/framework/data-sources)
- [HashiCorp Provider Design Principles](https://developer.hashicorp.com/terraform/plugin/best-practices/hashicorp-provider-design-principles)

The download contains SKILL.md . Extract the whole bundle; the supporting files are required. Inspect the included MANIFEST.json for file hashes.

By **HashiCorp**. [Exact upstream source ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/provider-resources/SKILL.md) · [Licence](/resources/skills/hashicorp-provider-resources/LICENSE.txt) · [Attribution](/resources/skills/hashicorp-provider-resources/ATTRIBUTION.txt)

SHA-256 3f87a1c9e8b8313f66a6db26d340b53faf4e51448f69227afafc1144b85d50c6

 Read the applicable licence Mozilla Public License Version 2.0
==================================

1. Definitions
--------------

1.1. "Contributor"
 means each individual or legal entity that creates, contributes to
 the creation of, or owns Covered Software.

1.2. "Contributor Version"
 means the combination of the Contributions of others (if any) used
 by a Contributor and that particular Contributor's Contribution.

1.3. "Contribution"
 means Covered Software of a particular Contributor.

1.4. "Covered Software"
 means Source Code Form to which the initial Contributor has attached
 the notice in Exhibit A, the Executable Form of such Source Code
 Form, and Modifications of such Source Code Form, in each case
 including portions thereof.

1.5. "Incompatible With Secondary Licenses"
 means

 (a) that the initial Contributor has attached the notice described
 in Exhibit B to the Covered Software; or

 (b) that the Covered Software was made available under the terms of
 version 1.1 or earlier of the License, but not also under the
 terms of a Secondary License.

1.6. "Executable Form"
 means any form of the work other than Source Code Form.

1.7. "Larger Work"
 means a work that combines Covered Software with other material, in
 a separate file or files, that is not Covered Software.

1.8. "License"
 means this document.

1.9. "Licensable"
 means having the right to grant, to the maximum extent possible,
 whether at the time of the initial grant or subsequently, any and
 all of the rights conveyed by this License.

1.10. "Modifications"
 means any of the following:

 (a) any file in Source Code Form that results from an addition to,
 deletion from, or modification of the contents of Covered
 Software; or

 (b) any new file in Source Code Form that contains any Covered
 Software.

1.11. "Patent Claims" of a Contributor
 means any patent claim(s), including without limitation, method,
 process, and apparatus claims, in any patent Licensable by such
 Contributor that would be infringed, but for the grant of the
 License, by the making, using, selling, offering for sale, having
 made, import, or transfer of either its Contributions or its
 Contributor Version.

1.12. "Secondary License"
 means either the GNU General Public License, Version 2.0, the GNU
 Lesser General Public License, Version 2.1, the GNU Affero General
 Public License, Version 3.0, or any later versions of those
 licenses.

1.13. "Source Code Form"
 means the form of the work preferred for making modifications.

1.14. "You" (or "Your")
 means an individual or a legal entity exercising rights under this
 License. For legal entities, "You" includes any entity that
 controls, is controlled by, or is under common control with You. For
 purposes of this definition, "control" means (a) the power, direct
 or indirect, to cause the direction or management of such entity,
 whether by contract or otherwise, or (b) ownership of more than
 fifty percent (50%) of the outstanding shares or beneficial
 ownership of such entity.

2. License Grants and Conditions
--------------------------------

2.1. Grants

Each Contributor hereby grants You a world-wide, royalty-free,
non-exclusive license:

(a) under intellectual property rights (other than patent or trademark)
 Licensable by such Contributor to use, reproduce, make available,
 modify, display, perform, distribute, and otherwise exploit its
 Contributions, either on an unmodified basis, with Modifications, or
 as part of a Larger Work; and

(b) under Patent Claims of such Contributor to make, use, sell, offer
 for sale, have made, import, and otherwise transfer either its
 Contributions or its Contributor Version.

2.2. Effective Date

The licenses granted in Section 2.1 with respect to any Contribution
become effective for each Contribution on the date the Contributor first
distributes such Contribution.

2.3. Limitations on Grant Scope

The licenses granted in this Section 2 are the only rights granted under
this License. No additional rights or licenses will be implied from the
distribution or licensing of Covered Software under this License.
Notwithstanding Section 2.1(b) above, no patent license is granted by a
Contributor:

(a) for any code that a Contributor has removed from Covered Software;
 or

(b) for infringements caused by: (i) Your and any other third party's
 modifications of Covered Software, or (ii) the combination of its
 Contributions with other software (except as part of its Contributor
 Version); or

(c) under Patent Claims infringed by Covered Software in the absence of
 its Contributions.

This License does not grant any rights in the trademarks, service marks,
or logos of any Contributor (except as may be necessary to comply with
the notice requirements in Section 3.4).

2.4. Subsequent Licenses

No Contributor makes additional grants as a result of Your choice to
distribute the Covered Software under a subsequent version of this
License (see Section 10.2) or under the terms of a Secondary License (if
permitted under the terms of Section 3.3).

2.5. Representation

Each Contributor represents that the Contributor believes its
Contributions are its original creation(s) or it has sufficient rights
to grant the rights to its Contributions conveyed by this License.

2.6. Fair Use

This License is not intended to limit any rights You have under
applicable copyright doctrines of fair use, fair dealing, or other
equivalents.

2.7. Conditions

Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
in Section 2.1.

3. Responsibilities
-------------------

3.1. Distribution of Source Form

All distribution of Covered Software in Source Code Form, including any
Modifications that You create or to which You contribute, must be under
the terms of this License. You must inform recipients that the Source
Code Form of the Covered Software is governed by the terms of this
License, and how they can obtain a copy of this License. You may not
attempt to alter or restrict the recipients' rights in the Source Code
Form.

3.2. Distribution of Executable Form

If You distribute Covered Software in Executable Form then:

(a) such Covered Software must also be made available in Source Code
 Form, as described in Section 3.1, and You must inform recipients of
 the Executable Form how they can obtain a copy of such Source Code
 Form by reasonable means in a timely manner, at a charge no more
 than the cost of distribution to the recipient; and

(b) You may distribute such Executable Form under the terms of this
 License, or sublicense it under different terms, provided that the
 license for the Executable Form does not attempt to limit or alter
 the recipients' rights in the Source Code Form under this License.

3.3. Distribution of a Larger Work

You may create and distribute a Larger Work under terms of Your choice,
provided that You also comply with the requirements of this License for
the Covered Software. If the Larger Work is a combination of Covered
Software with a work governed by one or more Secondary Licenses, and the
Covered Software is not Incompatible With Secondary Licenses, this
License permits You to additionally distribute such Covered Software
under the terms of such Secondary License(s), so that the recipient of
the Larger Work may, at their option, further distribute the Covered
Software under the terms of either this License or such Secondary
License(s).

3.4. Notices

You may not remove or alter the substance of any license notices
(including copyright notices, patent notices, disclaimers of warranty,
or limitations of liability) contained within the Source Code Form of
the Covered Software, except that You may alter any license notices to
the extent required to remedy known factual inaccuracies.

3.5. Application of Additional Terms

You may choose to offer, and to charge a fee for, warranty, support,
indemnity or liability obligations to one or more recipients of Covered
Software. However, You may do so only on Your own behalf, and not on
behalf of any Contributor. You must make it absolutely clear that any
such warranty, support, indemnity, or liability obligation is offered by
You alone, and You hereby agree to indemnify every Contributor for any
liability incurred by such Contributor as a result of warranty, support,
indemnity or liability terms You offer. You may include additional
disclaimers of warranty and limitations of liability specific to any
jurisdiction.

4. Inability to Comply Due to Statute or Regulation
---------------------------------------------------

If it is impossible for You to comply with any of the terms of this
License with respect to some or all of the Covered Software due to
statute, judicial order, or regulation then You must: (a) comply with
the terms of this License to the maximum extent possible; and (b)
describe the limitations and the code they affect. Such description must
be placed in a text file included with all distributions of the Covered
Software under this License. Except to the extent prohibited by statute
or regulation, such description must be sufficiently detailed for a
recipient of ordinary skill to be able to understand it.

5. Termination
--------------

5.1. The rights granted under this License will terminate automatically
if You fail to comply with any of its terms. However, if You become
compliant, then the rights granted under this License from a particular
Contributor are reinstated (a) provisionally, unless and until such
Contributor explicitly and finally terminates Your grants, and (b) on an
ongoing basis, if such Contributor fails to notify You of the
non-compliance by some reasonable means prior to 60 days after You have
come back into compliance. Moreover, Your grants from a particular
Contributor are reinstated on an ongoing basis if such Contributor
notifies You of the non-compliance by some reasonable means, this is the
first time You have received notice of non-compliance with this License
from such Contributor, and You become compliant prior to 30 days after
Your receipt of the notice.

5.2. If You initiate litigation against any entity by asserting a patent
infringement claim (excluding declaratory judgment actions,
counter-claims, and cross-claims) alleging that a Contributor Version
directly or indirectly infringes any patent, then the rights granted to
You by any and all Contributors for the Covered Software under Section
2.1 of this License shall terminate.

5.3. In the event of termination under Sections 5.1 or 5.2 above, all
end user license agreements (excluding distributors and resellers) which
have been validly granted by You or Your distributors under this License
prior to termination shall survive termination.

************************************************************************
* *
* 6. Disclaimer of Warranty *
* ------------------------- *
* *
* Covered Software is provided under this License on an "as is" *
* basis, without warranty of any kind, either expressed, implied, or *
* statutory, including, without limitation, warranties that the *
* Covered Software is free of defects, merchantable, fit for a *
* particular purpose or non-infringing. The entire risk as to the *
* quality and performance of the Covered Software is with You. *
* Should any Covered Software prove defective in any respect, You *
* (not any Contributor) assume the cost of any necessary servicing, *
* repair, or correction. This disclaimer of warranty constitutes an *
* essential part of this License. No use of any Covered Software is *
* authorized under this License except under this disclaimer. *
* *
************************************************************************

************************************************************************
* *
* 7. Limitation of Liability *
* -------------------------- *
* *
* Under no circumstances and under no legal theory, whether tort *
* (including negligence), contract, or otherwise, shall any *
* Contributor, or anyone who distributes Covered Software as *
* permitted above, be liable to You for any direct, indirect, *
* special, incidental, or consequential damages of any character *
* including, without limitation, damages for lost profits, loss of *
* goodwill, work stoppage, computer failure or malfunction, or any *
* and all other commercial damages or losses, even if such party *
* shall have been informed of the possibility of such damages. This *
* limitation of liability shall not apply to liability for death or *
* personal injury resulting from such party's negligence to the *
* extent applicable law prohibits such limitation. Some *
* jurisdictions do not allow the exclusion or limitation of *
* incidental or consequential damages, so this exclusion and *
* limitation may not apply to You. *
* *
************************************************************************

8. Litigation
-------------

Any litigation relating to this License may be brought only in the
courts of a jurisdiction where the defendant maintains its principal
place of business and such litigation shall be governed by laws of that
jurisdiction, without reference to its conflict-of-law provisions.
Nothing in this Section shall prevent a party's ability to bring
cross-claims or counter-claims.

9. Miscellaneous
----------------

This License represents the complete agreement concerning the subject
matter hereof. If any provision of this License is held to be
unenforceable, such provision shall be reformed only to the extent
necessary to make it enforceable. Any law or regulation which provides
that the language of a contract shall be construed against the drafter
shall not be used to construe this License against a Contributor.

10. Versions of the License
---------------------------

10.1. New Versions

Mozilla Foundation is the license steward. Except as provided in Section
10.3, no one other than the license steward has the right to modify or
publish new versions of this License. Each version will be given a
distinguishing version number.

10.2. Effect of New Versions

You may distribute the Covered Software under the terms of the version
of the License under which You originally received the Covered Software,
or under the terms of any subsequent version published by the license
steward.

10.3. Modified Versions

If you create software not governed by this License, and you want to
create a new license for such software, you may create and use a
modified version of this License if you rename the license and remove
any references to the name of the license steward (except to note that
such modified license differs from this License).

10.4. Distributing Source Code Form that is Incompatible With Secondary
Licenses

If You choose to distribute Source Code Form that is Incompatible With
Secondary Licenses under the terms of this version of the License, the
notice described in Exhibit B of this License must be attached.

Exhibit A - Source Code Form License Notice
-------------------------------------------

 This Source Code Form is subject to the terms of the Mozilla Public
 License, v. 2.0. If a copy of the MPL was not distributed with this
 file, You can obtain one at https://mozilla.org/MPL/2.0/.

If it is not possible or desirable to put the notice in a particular
file, then You may include the notice in a location (such as a LICENSE
file in a relevant directory) where a recipient would be likely to look
for such a notice.

You may add additional accurate notices of copyright ownership.

Exhibit B - "Incompatible With Secondary Licenses" Notice
---------------------------------------------------------

 This Source Code Form is "Incompatible With Secondary Licenses", as
 defined by the Mozilla Public License, v. 2.0.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Skill definition ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/provider-resources/SKILL.md) Checked 2026-10-14 https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/provider-resources/SKILL.md Supports: Workflow and stated scope
- [Repository licence ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/LICENSE) Checked 2026-10-07 https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/LICENSE Supports: Redistribution terms
- [Install instructions ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/README.md) Checked 2026-10-07 https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/README.md Supports: Documented install command
- [Pinned continuation review C2-W41 ↗](https://raw.githubusercontent.com/hashicorp/agent-skills/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/provider-resources/SKILL.md) Checked 2026-10-15 https://raw.githubusercontent.com/hashicorp/agent-skills/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/provider-resources/SKILL.md Supports: review.findings, bestFor

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Provider actions ↗ Guides Terraform Plugin Framework action registration, configuration and lifecycle-trigger integration.](/skills/hashicorp-provider-actions/)[### Provider configuration ↗ Builds a provider Configure method as a credential chain and names every source a failed login tried.](/skills/hashicorp-provider-configuration/)[### Provider framework migration ↗ Starts by asking whether to migrate at all, then muxes the provider and verifies before claiming the port is done.](/skills/hashicorp-provider-framework-migration/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Choose a toolkit](/tools/)
- [Inspect execution hosts](/agents/)
- [Check tool access](/mcp-servers/)
- [Check project dependencies](/check-repo/)