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

Hey Weston, thanks so much for the PR! Luke has added some comments which were addressed, now we need to find an engineering resource to review, which I'm sure you know is time consuming! We've added it to our triage list

thank you for the merge of #44 - what’s the release process? or is there another way for me to start using this feature?

<@U02PHEE59A6> if you want to use it right away, there's an alpha release:

<https://github.com/pulumi/pulumi-command/runs/5459717858?check_suite_focus=true#step:10:69>

You'll need to use the git sha for the SDK, and the `pulumi plugin install command &lt;version&gt;`

would I use `v0.0.4-alpha.1646714993+eb1d83ef` as the version?

for the `pulumi plugin install` command? yep

```pulumi plugin install resource command v0.0.4-alpha.1646714993+eb1d83ef
[resource plugin command-0.0.4-alpha.1646714993+eb1d83ef] installing
Downloading plugin: 4.36 MiB / 10.40 MiB [==========&gt;---------------]  41.93% 1s```

<@UCWG26BH7> since there’s still no release for this, question about whether or not pulumi knows how to get the correct plugin version from the go mod file? How does that work?
I’d prefer if I didn’t have to tell people that there’s an extra step in the setup process

How does Pulumi know where to get the binary?

It's resolved by the engine from your go module file. 