I'm trying to create a custom component for our company to use. I've got everything working just fine, but I have not been able to test it locally because of the plugin. If I publish the binaries to our github, everything works as expected. But if I want to make a change and just test it on a local project, I have not been able to figure out a way to run it without publishing everything to github. Currently I have been able to run

pulumi plugin install resource xyz v0.0.1 -f /bin/pulumi-resource-xyz

and now I just get an error about a pulumiplugin.yaml file not existing. I have not been able to find any documentation on this at all. Is there a step missing? Can someone provide some help or a link to some documentation that would be helpful?

Just put the plugin binary on PATH, or use

plugin install --file

to copy the file to the local plugin cache.

Sorry, what do you mean when you say "put the binary on PATH"? Also, isn't the second command basically what I have already tried?

"PATH" as in the environment variable telling your shell where to find executables. e.g. likely you'll have C:\Users\Aaron\go\bin as a directory listed in PATH (or Path for windows) and if the plugin exe is in that folder it should get picked up. and yes

--file

is the same as

-f

, I think that expects to be pointed to the file itself, (i.e. pulumi-resource-xyz.exe) not the folder.

Ok, thanks. Sadly I have done both of those to no avail.

does anything get copied to ".pulumi/plugins" when you run install?

Yes

did your original file have an extension?

No

ah well that's probably the issue. The windows code will be expecting to find an ".exe" file

Makes sense, the error indicates that it is still able to use that file though.

yeh it should, how are you building the plugin?

just running

make install_provider

https://github.com/pulumi/pulumi-provider-boilerplate <- that one?

I'd raise an issue on that repo, sounds like a makefile bug. Building the provider on windows ought to be an .exe file.

Hmm... ok, thanks. I did have to change a lot about this template to make it work. The only real change to the makefile was the property parameter on building the dotnet sdk.

no, the one your using should be the more recent and up-to date one. It's probably not been tested well on windows.

ah ok