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

skandio___skand_platform_backend___Pipelines_—_Bitbucket.png

Hi all, has anyone encountered this issue that when pulumi up,  it automatically install the resource plugin but try to find another version of it

And I believe it’s similar to this <https://github.com/pulumi/pulumi/issues/5641#issuecomment-735867087>

this is odd. what do you get when `pulumi plugin ls` ?

That happens to me when an old resource still has a reference to the old version of the provider. It usually sorts itself out by installing the version that didn't get automatically installed. After a couple more `up`s, the references to the old provider are all gone and everything's back to normal.

skandio___skand_platform_backend___Pipelines_—_Bitbucket-2.png

I tried to `pulumi destory` everything and `pulumi up` again and it didn’t install any plugin this time.

Do I need to install provider plugin manually?

At least for now give it a go and try installing the plugins manually.

It’s fixed by manually install the plugin but it would be great if we don’t have to specify the version.

Thank you <@U022S4W6W00> and <@U012UJTT55M>

Glad to hear this is fixed. If this happens again, could you let us know please? Our CLI should normally download all the necessary materials for running the app.