Resources
Resources are an abstraction that allow Terraform to manage infrastructure objects by defining create, read, update, and delete functionality that maps onto API operations. Resource schemas define what fields a resource has, give Terraform metadata about those fields, and define how the resource behaves. Refer to Resources in the Framework documentation for details.
This page explains how to migrate a resource's schema from SDKv2 to the plugin Framework. We also recommend reviewing these additional guides for resources throughout the migration:
- Create, Read, Update, and Delete functions: The resource defines the logic to manage resources with Terraform.
- Default: The resource specifies default values for attributes that are null within the configuration.
- Import: The resource defines the logic to add a resource to Terraform's state.
- Plan modification: The resource customizes the Terraform plan for known values or behaviors outside the practitioner's configuration.
- State upgrade: The resource updates Terraform state information in advanced use cases.
- Timeouts: The resource uses timeouts during create, read, update or delete operations.
SDKv2
In SDKv2, resources are defined by the ResourcesMap
field in the schema.Provider
struct, which maps resource names
(strings) to their schema. Each schema is a schema.Resource
struct that includes:
- A
Schema
field, which defines resource attributes - Fields for resource lifecycle functions such as
Create
andCreateContext
- Fields for functions to implement state upgrade (
StateUpgraders
), import (Importer
), and customize diff (CustomizeDiff
)
The following code shows a basic implementation of resource schema with SDKv2.
SDKv2 defines the schema.Resource
struct as follows.
Framework
In the Framework, you define your provider's resources by adding them to your provider's Resources
method.
The Resources
method on your provider.Provider
returns a slice of functions that return types that
implement the resource.Resource
interface for each resource your provider supports.
The following code shows how you add a resource to your provider with the Framework.
The resource.Resource
interface requires Metadata
, Schema
, Create
, Read
, Update
, and Delete
methods.
The Schema
method returns a schema.Schema
struct which defines your resource's attributes.
The Metadata
method returns a type name that you define.
The following code shows how you define a resource.Resource
which implements these methods with the
Framework.
Refer to the Resources - CRUD functions page in this guide to learn how to
implement the resource.Resource
interface.
Migration Notes
Remember the following differences between SDKv2 and the Framework when completing the migration.
- SDKv2 uses
schema.Resource
structs to define resources. These structs have aSchema
field which holds aschema.Schema
to define the resource's attributes and behavior. In the Framework, you define a type that implements theresource.Resource
interface, which includes aSchema
method that returns your resource's schema. - SDKv2 implements a resource's CRUD operations as functions on the
schema.Resource
. In the Framework, you define a type that implements theresource.Resource
interface. The resource interface contains the functions that define your resource's CRUD operations. - SDKv2 by default demotes certain resource schema definition and data consistency errors to only be visible as Terraform warning logs. After migration, these errors will always be visible to practitioners and prevent further Terraform operations. The SDKv2 resource data consistency errors documentation discusses how to find these errors in SDKv2 resources and potential solutions prior to migrating. See the CRUD - Resolving Data Consistency Errors section for Plugin Framework solutions during migration.
Example
SDKv2
In SDKv2, the ResourcesMap
field on the schema.Provider
struct holds a map[string]*schemaResource
. A typical
pattern is to implement a function that returns schema.Resource
.
This code defines the example_resource
resource by mapping the resource name to the exampleResource
struct.
Framework
The following shows the same section of provider code after the migration.
This code defines the Schema
and Metadata
methods for the Resource
.