Data Source Type Not Found or Resource Type Not Found when using Terraform 1.6

[austinvalle]

This is a Framework bug affecting users of Terraform 1.6 using providers built using Plugin Framework 1.4.0. The root cause is the recent caching functionality being enabled in #828.

Module version

github.com/hashicorp/terraform-plugin-framework v1.4.0

Relevant provider source code

Any resource/data source schema will have this problem, sample:

resp.Schema = schema.Schema{
	Attributes: map[string]schema.Attribute{
		"configurable_attribute": schema.StringAttribute{
			MarkdownDescription: "Example configurable attribute",
			Required:            true,
		},
	},
}

Terraform Configuration Files

resource "examplecloud_thing" "this" {
  configurable_attribute = "test"
}

data "examplecloud_thing" "this" {
  configurable_attribute = "test"
}

Expected Behavior

Resource/Data Source type is found and RPCs correctly validate/plan/apply

Actual Behavior

An error diagnostic is returned:

 $ terraform1.6 apply -auto-approve
╷
│ Error: Resource Type Not Found
│ 
│   with examplecloud_thing.this,
│   on resource.tf line 8, in resource "examplecloud_thing" "this":
│    8: resource "examplecloud_thing" "this" {
│ 
│ No resource type named "examplecloud_thing" was found in the provider.
╵
╷
│ Error: Data Source Type Not Found
│ 
│   with data.examplecloud_thing.this,
│   on resource.tf line 12, in data "examplecloud_thing" "this":
│   12: data "examplecloud_thing" "this" {
│ 
│ No data source type named "examplecloud_thing" was found in the provider.
╵

Workarounds

Either of the following will workaround the error

• For practitioners, they can downgrade to use Terraform 1.5.x

• For provider developers, they can downgrade terraform-plugin-framework to v1.3.5 AND terraform-plugin-go to v0.18.0.

  • If using terraform-plugin-mux, downgrade to v0.11.2 to avoid build errors from terraform-plugin-go
  • If using terraform-plugin-sdk/v2, downgrade to v2.28.0 to avoid build errors from terraform-plugin-go

Example of build error if you don't downgrade terraform-plugin-go and co.

# github.com/hashicorp/terraform-plugin-framework/internal/proto5server
../../go/pkg/mod/github.com/hashicorp/terraform-plugin-framework@v1.3.5/internal/proto5server/serve.go:14:34: cannot use &Server{} (value of type *Server) as tfprotov5.ProviderServer value in variable declaration: *Server does not implement tfprotov5.ProviderServer (missing method GetMetadata)
# github.com/hashicorp/terraform-plugin-framework/internal/proto6server
../../go/pkg/mod/github.com/hashicorp/terraform-plugin-framework@v1.3.5/internal/proto6server/serve.go:14:34: cannot use &Server{} (value of type *Server) as tfprotov6.ProviderServer value in variable declaration: *Server does not implement tfprotov6.ProviderServer (missing method GetMetadata)

References

• Custom provider built with terraform-plugin-framework does not find resource/data source types with TF 1.6 terraform#33990
• Error: Data Source Type Not Found when using dev_overrides and 1.6 terraform#34001

[austinvalle]

The fix for this issue has been released with terraform-plugin-framework v1.4.1 🚀

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.