Closed DCAL12 closed 1 year ago
Hi @DCAL12! Can you provide a few more details on the existing Pulumi program for which you attempted to upgrade the was-static-website
component? It sounds like you had an existing Pulumi program using version 0.3.0 and then upgraded to 0.4.0 using npm
, but did you update package.json
and package-lock.json
with the new version as well?
Closing due to inactivity
What happened?
I attempted upgrade to
@pulumi/aws-static-website
^0.4.0
(via NPM), but pulumi commands are still using pluginresource plugin aws-static-website-0.3.0
Expected Behavior
Pulumi CLI uses resource plugin matching the installed NPM version
Steps to reproduce
npm install @pulumi/aws-static-website@0.4.0
pulumi up
Output of
pulumi about
Additional context
As a workaround, I am able to run
pulumi plugin install resource aws-static-website 0.4.0
afternpm install
but beforepulumi up
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).