Second question of the day... Is there an explanation to when I need to install plugin and when I don't? I thought they were installed automatically when I installed the NPM packages, but now it seems like I miss one package in my when I run the application (it is an automation application). I know I can just install it manually, but I don't feel there is a consistent behavior around when I need to install plugins.

I think this post helps clarify the difference between plugins and the SDKs for providers https://www.pulumi.com/blog/dynamic-providers/

That is all good, but I thought the plugins were installed together with the SDKs, or do we need to install the plugins manually? I feel like we sometimes need to install the plugin and sometimes they are just there, so I think some clarification on how it is working (or should be working) would be really nice 🙂

So there is some logic built into our packages to resolve plugins - if the plug-in is not installed then it’s a bug

we sort of see that all the time I would say. So I'll file a bug for it.

Yes please do - if there’s a consistent issue here, we should look into it

@broad-dog-22463 Are they resolved during

npm install

or runtime? If they are resolved during npm install I understand why we get this issue and the problem is on me (except maybe for some lacking documentation 🙂 )

Yes it’s during npm install :)

got it... We built the application and then copied the app to a container, that will of course not include the plugins since they aren't installed in the application folder.