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

Is this the recommended way to test custom providers written in go? <https://github.com/pulumi/providertest>

It is. But note that it also contains <https://github.com/pulumi/providertest/tree/main/pulumitest|pulumitest>, which is probably easier for most scenarios. Also note that all of this is v0.* so breaking changes may occur.

Thanks! Yeah I’ve noticed a few rough edges playing around with the go provider stuff but nothing too bad

I’ve been looking into this today. I built a provider using <http://github.com/pulumi/pulumi-go-provider|github.com/pulumi/pulumi-go-provider> and I’m trying to attach it using an <http://github.com/pulumi/providertest/pulumitest/opttest|github.com/pulumi/providertest/pulumitest/opttest> `AttachProviderServer` option. Is it possible to return a `pulumirpc.ResourceProviderServer` from a provider created using the `infer` package? Or do I need to compile the binary first and use `AttachProviderBinary` instead?