Issues with List Development

[remyleone]

I’m having issue with developing list support for my provider.

When I try to run a test I get an error like this one:

    vpc_list_test.go:17: Step 2/2 error running query checks: running terraform query command returned diagnostics: [{baseLogMessage:{Lvl:error Msg:Error: Resource Type Not Found Time:2026-02-25 15:44:29.518763 +0100 CET} Diagnostic:{Severity:error Summary:Resource Type Not Found Detail:No resource type named "scaleway_vpc" was found in the provider. Range:0x4d0ea7508ec0 Snippet:0x4d0ea7580e10}} {baseLogMessage:{Lvl:error Msg:Error: Resource Type Not Found Time:2026-02-25 15:44:29.518843 +0100 CET} Diagnostic:{Severity:error Summary:Resource Type Not Found Detail:No resource type named "scaleway_vpc" was found in the provider. Range:0x4d0ea7508f40 Snippet:0x4d0ea7580e60}} {baseLogMessage:{Lvl:error Msg:Error: Resource Type Not Found Time:2026-02-25 15:44:29.518918 +0100 CET} Diagnostic:{Severity:error Summary:Resource Type Not Found Detail:No resource type named "scaleway_vpc" was found in the provider. Range:0x4d0ea7508fc0 Snippet:0x4d0ea7580eb0}}]

But when I export the schema of my provider, this list resource does indeed show up

Is there any way to debug this kind of issue?

Here is my draft PR if you want to reproduce locally. feat(vpc): add support for list resource by remyleone · Pull Request #3709 · scaleway/terraform-provider-scaleway · GitHub

[jbardin]

Hi @remyleone,

I haven’t built a list resource with the framework myself yet, but I think the error being Resource Type Not Found as opposed to List Resource Type Not Found indicates that you are missing the managed version of that resource in the implementation. I don’t know exactly where the cross-referencing is happening in the framework, but a list resource does depend on it’s managed counterpart at a minimum to build the schema.

[remyleone]

The resource scaleway_vpc is also present in the provider. So I’m not sure what is wrong here.

[jbardin]

I think it has something to do with the managed resource coming from the SDK server and not the Framework server, but I’m still piecing together how the mux builds the schemas in there.