No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

There's a few gotchas with plugin resolution. Is `pulumi-resource-checkmate` in PATH? e.g. `which pulumi-resource-checkmate` - if it is, it will be used instead of the installed one.

it isn't
```% which pulumi-resource-checkmate
pulumi-resource-checkmate not found```

The other bit is the SDK. Are you driving it from Node or some other language?

Is the node SDK versioned itself? Pulumi will be trying to ensure that the version of the Node SDK has a matching resource plugin with the same version. Guessing it's versioned 0.1.5?

yeah its got version: 0.1.5 in the package.json if thats what you mean

Ah yes hm.. so that's why it's looking for 0.1.5, the strange part is why it's finding 0.0.1..

so is that the version reported from the plugin itself then?

I've checked PF sources just in case there's some debug code injecting 0.0.1 but doesn't seem to be

you can run your program with `PULUMI_DEBUG_GRPC=$PWD/log.json pulumi up` and I think one of the calls should show the version it's reporting back

`{"method":"/pulumirpc.ResourceProvider/GetPluginInfo","request":{},"response":{"version":"0.0.1"},"metadata":{"kind":"resource","mode":"client","name":"checkmate"}}`

oh wait i think i found it. it comes from the `ProviderInfo`

Is it something we can fix in pulumi-terraform-bridge repo?

no i think i just didn't set it right. will report back after i rebuild haha