hi! i'm experiencing something really strange. i h...
# typescript
f
hi! i'm experiencing something really strange. i have a pulumi ts project, with aws provider version 6.33 in the package-lock.json and version set to
^6.0.0
in package.json. yet when i run pulumi up, it seems to want to downgrade the provider to 5.43, but i don't see that 5.43 anywhere in the codebase. i tried doing
pulumi plugin rm --all
and deleted
node_modules
, re-ran
npm install
and
pulumi preview
to no avail. any ideas what could be bringing back this old plugin version in a newer project? it looks like this
Copy code
~ pulumi:providers:aws: (update)
        [id=some-uuid-foo]
        [urn=urn:pulumi:staging::myapp-pulumi::pulumi:providers:aws::aws-us-east-1]
      ~ version                  : "6.33.0" => "5.43.0"
and it's reflected in some resource updates too in case it matters, this project is actually pretty new so it has always been set to 6.0.0, but other projects at my work might have had 5.x. thanks for any help anyone can provide!
f
That's very odd. Somewhere, somehow, pulumi is picking up an old version of that provider to run; despite what's in node_modules. I believe the OS-level
pulumi
cli downloads providers to somewhere outside node_modules; and so there can be drift, but I would have expected your
pulumi plugin rm --all
command to cover that.
f
so yeah, when i ran that it cleared things out but after running
pulumi preview
again i somehow ended up with multiple versions
Copy code
$ pulumi plugin ls
NAME        KIND      VERSION  SIZE    INSTALLED       LAST USED
aws         resource  6.41.0   775 MB  15 minutes ago  13 minutes ago
aws         resource  6.33.0   744 MB  15 minutes ago  13 minutes ago
aws         resource  6.32.0   701 MB  15 minutes ago  13 minutes ago
aws         resource  5.43.0   547 MB  15 minutes ago  13 minutes ago
aws-native  resource  0.56.0   94 MB   16 minutes ago  13 minutes ago
awsx        resource  2.9.0    76 MB   16 minutes ago  13 minutes ago
awsx        resource  1.0.2    86 MB   16 minutes ago  13 minutes ago
docker      resource  4.5.3    50 MB   16 minutes ago  13 minutes ago
docker      resource  3.6.1    40 MB   16 minutes ago  13 minutes ago
tls         resource  4.10.0   34 MB   16 minutes ago  13 minutes ago

TOTAL plugin cache size: 3.1 GB
hm we do have a private component library that we're using via
npm link
so i wonder if something funky happened there.
ahh... i think it was that
i did
rm -rf node_modules
in the component library and reran npm install and things seem better
but idk why it was picking that up to begin with