Implement data source

12min
|
Terraform

In this tutorial, you will implement a data source to read the list of coffees from the HashiCups API and save it in Terraform’s state. To do this, you will:

Define the initial data source type.
This prepares the data source to be added to the provider.
Add data source to provider.
This enables the data source for testing and Terraform configuration usage.
Implement the HashiCups client in the data source.
This retrieves the configured HashiCups client from the provider and makes it available for data source operations.
Define the data source schema.
This prepares the data source to set Terraform state with the list of coffees.
Define the data source data model.
This models the data source schema as a Go type so the data is accessible for other Go code.
Define the data source read logic.
This handles calling the HashiCups API using the configured client and setting the Terraform state with the data.
Verify data source behavior.
This ensures the expected data source behavior.

Prerequisites

To follow this tutorial, you need:

Go 1.21+ installed and configured.
Terraform v1.8+ installed locally.
Docker and Docker Compose to run an instance of HashiCups locally.

Navigate to your terraform-provider-hashicups directory.

Your code should match the 02-provider-configure directory from the example repository.

If you haven't already done so, clone the Terraform HashiCups Provider repository.

$ git clone https://github.com/hashicorp/terraform-provider-hashicups

Change into the 02-provider-configure directory of cloned repository.

$ cd terraform-provider-hashicups/02-provider-configure

Then, install all the provider's dependencies.

$ go mod tidy

Build the provider

Terraform installs providers and verifies their versions and checksums when you run terraform init. Terraform will download your providers from either the provider registry or a local registry. However, while building your provider you will want to test Terraform configuration against a local development build of the provider. The development build will not have an associated version number or an official set of checksums listed in a provider registry.

Terraform allows you to use local provider builds by setting a dev_overrides block in a configuration file called .terraformrc. This block overrides all other configured installation methods.

Terraform searches for the .terraformrc file in your home directory and applies any configuration settings you set.

First, find the GOBIN path where Go installs your binaries. Your path may vary depending on how your Go environment variables are configured.

$ go env GOBIN/Users/<Username>/go/bin

If the GOBIN go environment variable is not set, use the default path, /Users/<Username>/go/bin.

Create a new file called .terraformrc in the root directory (~), then add the dev_overrides block below. Change the <PATH> to the value returned from the echo $GOBIN command above.

provider_installation {   dev_overrides {    "hashicorp.com/edu/hashicups" = "<PATH>"  }   # For all other providers, install them directly from their origin provider  # registries as normal. If you omit this, Terraform will _only_ use  # the dev_overrides block, and so no other providers will be available.  direct {}}

You must create your CLI configuration file in your user %APPDATA% root directory. The physical location of this directory depends on your Windows version and system configuration.

Search for the user environment variables in PowerShell to find its location on your system.

$ $env:APPDATA

In another terminal, change into the directory returned from the command above.

Find the GOBIN path where go installs your binaries. Your path may vary depending on how your Go environment variables are configured.

$ go env GOBIN/Users/<Username>/go/bin

If the GOBIN go environment variable is not set, use the default path, /Users/<Username>/go/bin.

Create a new file called terraform.rc and add the dev_overrides block below. Change the <PATH> to the value returned from the go env GOBIN command above.

provider_installation {   dev_overrides {    "hashicorp.com/edu/hashicups" = "<PATH>"  }   # For all other providers, install them directly from their origin provider  # registries as normal. If you omit this, Terraform will _only_ use  # the dev_overrides block, and so no other providers will be available.  direct {}}

Start HashiCups locally

Your HashiCups provider requires a running instance of HashiCups. Navigate to the docker_compose directory.

$ cd docker_compose

Run docker-compose up to spin up a local instance of HashiCups on port 19090.

$ docker-compose up

Leave this process running in your terminal window. The HashiCups service will print out log messages in this terminal.

In the original terminal window, verify that HashiCups is running by sending a request to its health check endpoint. The HashiCups service will respond with ok.

$ curl localhost:19090/health/readyzok

Create a HashiCups user

HashiCups requires a username and password to generate a JSON web token (JWT) which is used to authenticate against protected endpoints. You will use this user to authenticate to the HashiCups provider to manage your orders.

Create a user on HashiCups named education with the password test123.

$ curl -X POST localhost:19090/signup -d '{"username":"education", "password":"test123"}'{"UserID":1,"Username":"education","token":"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE1OTEwNzgwODUsInVzZXJfaWQiOjIsInVzZXJuYW1lIjoiZWR1Y2F0aW9uIn0.CguceCNILKdjOQ7Gx0u4UAMlOTaH3Dw-fsll2iXDrYU"}

Set the HASHICUPS_TOKEN environment variable to the token you retrieved from invoking the /signup endpoint. You will use this later in the tutorial to verify that Terraform has created your HashiCups order.

$ export HASHICUPS_TOKEN=ey...

The terminal containing your HashiCups logs will record the sign up operation.

api_1  | 2020-12-10T09:19:50.601Z [INFO]  Handle User | signup

Now that the HashiCups app is running, you are ready to start working on the Terraform provider.

Implement initial data source type

To add a new data source to your provider, start by creating a type that implements the datasource.DataSource interface.

This interface requires the following:

Metadata method. This defines the data source type name, which is how the data source is referred to in Terraform configurations.
Schema method. This defines the schema for any data source configuration and state data.
Read method. This defines the logic which sets the Terraform state for the data source.

Add a new data source that will load data about coffee drinks from the HashiCups API by creating a internal/provider/coffees_data_source.go file with the following.

package provider import (  "context"   "github.com/hashicorp/terraform-plugin-framework/datasource"  "github.com/hashicorp/terraform-plugin-framework/datasource/schema") // Ensure the implementation satisfies the expected interfaces.var (  _ datasource.DataSource = &coffeesDataSource{}) // NewCoffeesDataSource is a helper function to simplify the provider implementation.func NewCoffeesDataSource() datasource.DataSource {  return &coffeesDataSource{}} // coffeesDataSource is the data source implementation.type coffeesDataSource struct{} // Metadata returns the data source type name.func (d *coffeesDataSource) Metadata(_ context.Context, req datasource.MetadataRequest, resp *datasource.MetadataResponse) {  resp.TypeName = req.ProviderTypeName + "_coffees"} // Schema defines the schema for the data source.func (d *coffeesDataSource) Schema(_ context.Context, _ datasource.SchemaRequest, resp *datasource.SchemaResponse) {  resp.Schema = schema.Schema{}} // Read refreshes the Terraform state with the latest data.func (d *coffeesDataSource) Read(ctx context.Context, req datasource.ReadRequest, resp *datasource.ReadResponse) {}

Add data source to provider

Providers use the DataSources method to define the data sources they implement.

Open the internal/provider/provider.go file.

Add your new data source by replacing the DataSources method with the following.

// DataSources defines the data sources implemented in the provider.func (p *hashicupsProvider) DataSources(_ context.Context) []func() datasource.DataSource {  return []func() datasource.DataSource {    NewCoffeesDataSource,  }}

Implement data source client functionality

Data sources use the optional Configure method to fetch configured clients from the provider. The provider configures the HashiCups client and the data source can save a reference to that client for its operations.

Open the internal/provider/coffees_data_source.go file.

Allow your data source type to store a reference to the HashiCups client by replacing the coffeesDataSource type with the following.

// coffeesDataSource is the data source implementation.type coffeesDataSource struct {  client *hashicups.Client}

Replace the import statement at the beginning of the file with the following.

import (  "context"   "github.com/hashicorp-demoapp/hashicups-client-go"  "github.com/hashicorp/terraform-plugin-framework/datasource"  "github.com/hashicorp/terraform-plugin-framework/datasource/schema")

Ensure that your data source implements the DataSourceWithConfigure interface by replacing the var ( ... ) statement with the following.

// Ensure the implementation satisfies the expected interfaces.var (  _ datasource.DataSource              = &coffeesDataSource{}  _ datasource.DataSourceWithConfigure = &coffeesDataSource{})

Fetch the HashiCups client from the provider by adding the Configure method to your data source type.

// Configure adds the provider configured client to the data source.func (d *coffeesDataSource) Configure(_ context.Context, req datasource.ConfigureRequest, resp *datasource.ConfigureResponse) {  // Add a nil check when handling ProviderData because Terraform  // sets that data after it calls the ConfigureProvider RPC.  if req.ProviderData == nil {    return  }   client, ok := req.ProviderData.(*hashicups.Client)  if !ok {    resp.Diagnostics.AddError(      "Unexpected Data Source Configure Type",      fmt.Sprintf("Expected *hashicups.Client, got: %T. Please report this issue to the provider developers.", req.ProviderData),    )     return  }   d.client = client}

Implement data source schema

The data source uses the Schema method to define the acceptable configuration and state attribute names and types. The coffees data source will need to save a list of coffees with various attributes to the state.

Replace your data source's Schema method with the following.

// Schema defines the schema for the data source.func (d *coffeesDataSource) Schema(_ context.Context, _ datasource.SchemaRequest, resp *datasource.SchemaResponse) {  resp.Schema = schema.Schema{    Attributes: map[string]schema.Attribute{      "coffees": schema.ListNestedAttribute{        Computed: true,        NestedObject: schema.NestedAttributeObject{          Attributes: map[string]schema.Attribute{            "id": schema.Int64Attribute{              Computed: true,            },            "name": schema.StringAttribute{              Computed: true,            },            "teaser": schema.StringAttribute{              Computed: true,            },            "description": schema.StringAttribute{              Computed: true,            },            "price": schema.Float64Attribute{              Computed: true,            },            "image": schema.StringAttribute{              Computed: true,            },            "ingredients": schema.ListNestedAttribute{              Computed: true,              NestedObject: schema.NestedAttributeObject{                Attributes: map[string]schema.Attribute{                  "id": schema.Int64Attribute{                    Computed: true,                  },                },              },            },          },        },      },    },  }}

Implement data source data models

Add data model types to your data source with the following.

// coffeesDataSourceModel maps the data source schema data.type coffeesDataSourceModel struct {    Coffees []coffeesModel `tfsdk:"coffees"`} // coffeesModel maps coffees schema data.type coffeesModel struct {    ID          types.Int64               `tfsdk:"id"`    Name        types.String              `tfsdk:"name"`    Teaser      types.String              `tfsdk:"teaser"`    Description types.String              `tfsdk:"description"`    Price       types.Float64             `tfsdk:"price"`    Image       types.String              `tfsdk:"image"`    Ingredients []coffeesIngredientsModel `tfsdk:"ingredients"`} // coffeesIngredientsModel maps coffee ingredients datatype coffeesIngredientsModel struct {    ID types.Int64 `tfsdk:"id"`}

Replace the import statement at the beginning of the file with the following.

import (  "context"  "fmt"   "github.com/hashicorp-demoapp/hashicups-client-go"  "github.com/hashicorp/terraform-plugin-framework/datasource"  "github.com/hashicorp/terraform-plugin-framework/datasource/schema"  "github.com/hashicorp/terraform-plugin-framework/types")

Implement read functionality

The data source uses the Read method to refresh the Terraform state based on the schema data. The hashicups_coffees data source will use the configured HashiCups client to call the HashiCups API coffee listing endpoint and save this data to the Terraform state.

The read method follows these steps:

Reads coffees list. The method invokes the API client's GetCoffees method.
Maps response body to schema attributes. After the method reads the coffees, it maps the []hashicups.Coffee response to coffeesModel so the data source can set the Terraform state.
Sets state with coffees list.

Replace your data source's Read method with the following.

// Read refreshes the Terraform state with the latest data.func (d *coffeesDataSource) Read(ctx context.Context, req datasource.ReadRequest, resp *datasource.ReadResponse) {    var state coffeesDataSourceModel     coffees, err := d.client.GetCoffees()    if err != nil {      resp.Diagnostics.AddError(        "Unable to Read HashiCups Coffees",        err.Error(),      )      return    }     // Map response body to model    for _, coffee := range coffees {      coffeeState := coffeesModel{        ID:          types.Int64Value(int64(coffee.ID)),        Name:        types.StringValue(coffee.Name),        Teaser:      types.StringValue(coffee.Teaser),        Description: types.StringValue(coffee.Description),        Price:       types.Float64Value(coffee.Price),        Image:       types.StringValue(coffee.Image),      }       for _, ingredient := range coffee.Ingredient {        coffeeState.Ingredients = append(coffeeState.Ingredients, coffeesIngredientsModel{          ID: types.Int64Value(int64(ingredient.ID)),        })      }       state.Coffees = append(state.Coffees, coffeeState)    }     // Set state    diags := resp.State.Set(ctx, &state)    resp.Diagnostics.Append(diags...)    if resp.Diagnostics.HasError() {      return    }}

Build and install the updated provider.

$ go install .

Verify data source

Navigate to the examples/coffees directory.

$ cd examples/coffees

The main.tf Terraform configuration file in this directory reads data from your new hashicups_coffees data source.

Add an output value to have Terraform print out that data.

terraform {  required_providers {    hashicups = {      source = "hashicorp.com/edu/hashicups"    }  }} provider "hashicups" {  host     = "http://localhost:19090"  username = "education"  password = "test123"} data "hashicups_coffees" "edu" {} output "edu_coffees" {  value = data.hashicups_coffees.edu}

Run a Terraform plan. Terraform will report the data it retrieved from the HashiCups API.

$ terraform plan##...data.hashicups_coffees.edu: Reading...data.hashicups_coffees.edu: Read complete after 0s Changes to Outputs:  + edu_coffees = {      + coffees = [          + {              + description = ""              + id          = 1              + image       = "/hashicorp.png"              + ingredients = [                  + {                      + id = 6                    },                ]              + name        = "HCP Aeropress"              + price       = 200              + teaser      = "Automation in a cup"            },##...You can apply this plan to save these new output values to the Terraform state,without changing any real infrastructure. ─────────────────────────────────────────────────────────────────────────────── Note: You didn't use the -out option to save this plan, so Terraform can'tguarantee to take exactly these actions if you run "terraform apply" now.

Navigate to the terraform-provider-hashicups directory.

$ cd ../..

Next steps

Congratulations! You have implemented a data source in the provider that uses the configured API client to save Terraform state.

If you were stuck during this tutorial, checkout the 03-read-coffees directory in the example repository to see the code implemented in this tutorial.

To learn more about the Terraform Plugin Framework, refer to the Terraform Plugin Framework documentation.
For a full capability comparison between the SDKv2 and the Plugin Framework, refer to the Which SDK Should I Use? documentation.
The example repository contains directories corresponding to each tutorial in this collection.
Submit any Terraform Plugin Framework bug reports or feature requests to the development team in the Terraform Plugin Framework Github repository.
Submit any Terraform Plugin Framework questions in the Terraform Plugin Framework Discuss forum.

Configure client

Logging