Documentation
¶
Overview ¶
Command importer-probe asks a real provider plugin, over the plugin protocol, whether a resource type has an Importer at all.
The question matters because a wire identity schema is not evidence that a type can be imported: issue #331 found aws_iam_policy_attachment admitted off its identity schema with no Importer behind it, so a real migrate hits "resource ... doesn't support import" the moment internal/live/projection calls ImportResourceState. Nothing static in this repository can see that - the provider's own documentation is the only other source, and it is silent for 6 types that do have Importers.
The measurement needs no cloud and no credentials. helper/schema's Provider.ImportState checks Importer == nil and terraform-plugin-framework answers "Resource Import Not Implemented" before either makes an API call, so a syntactically invalid import ID separates the two populations cleanly: a type WITH an Importer answers with a parse error, or succeeds outright where the Importer is a passthrough.
Usage: -exe names the provider binary (a plugin cache entry will do), -all sweeps every type the provider serves into -out. Without -all it prints the wire-only bucket (read from -sources, tools/row-gen's own live/identity-sources.json artifact by default) and four fixed controls.
Source Files