npm install ended grabbing a new version of the ku...
# general
o
npm install ended grabbing a new version of the kubernetes plugin just now but still no gcp
c
@orange-tailor-85423 npm should rope in whatever you need when you
npm install
what’s the specific error?
o
error: could not load plugin for gcp provider 'urnpulumicasey-robertson:rhaegarpulumiprovidersgcp:default': no resource plugin 'gcp' found in the workspace or on your $PATH
c
are you on a unix or windows
o
neither
npm install
or generic
pulumi plugin install
grab it
this is on unix (Mac OS)
c
can you
ls ~/.pulumi/plugins/
also
pulumi version
o
sure
ls ~/.pulumi/plugins resource-aws-v0.16.5 resource-kubernetes-v0.17.5-dev-1542413498-g2dae07c resource-aws-v0.16.6 resource-kubernetes-v0.18.0
c
ok so neither of them are there
o
pulumi version v0.16.14
correct - I just thought one of those methods would grab it
c
@bitter-oil-46081 do you have any ideas about this?
can I see your package.json?
o
sure
Copy code
{
  "name": "rhaegar",
  "description": "Infrastructure as code for building GCP IAM with Pulumi.",
  "dependencies": {
    "@pulumi/gcp": "^0.16.6",
    "@pulumi/kubernetes": "0.20.0",
    "@pulumi/pulumi": "^0.16.14",
    "config": "^2.0.1",
    "googleapis": "^34.0.0"
  }
}
c
lol what the heck.
o
lol
yep
c
mmmmmmm
what was the output of
npm install
?
o
no output - just warnings about missing repo and license field
c
oh also please use
"^0.20.1"
o
ok
c
there’s a bug in
0.20.0
you want to miss. 🙂
can you paste the output?
o
npm install
@echoing-match-29901/kubernetes@0.20.1 install /Users/casey.robertson/repos/azureDevOps/rhaegar/node_modules/@pulumi/kubernetes
node scripts/install-pulumi-plugin.js resource kubernetes v0.20.1
[resource plugin kubernetes-0.20.1] installing Downloading plugin: 16.70 MiB / 16.70 MiB [========================] 100.00% 1s npm WARN rhaegar@ No repository field. npm WARN rhaegar@ No license field.
c
sigh
ok this is a wild guess can you delete node_modules and package-lock.json and then re-install?
o
sure thing
ha now it grabbed them
doh - sorry for the hassle
c
😐
did not like.
something weird is going on,
o
something in the lock file?
I'm pretty noob to NPM still
c
no idea
o
I'll chalk it up to experience - coworker was writing a CI build and he was getting that error and I was able to repro after deleting my plugin
(but not deleting my node_modules and package-lock.json)
c
oh you deleted it on purpose?
that is probably it.
w
Note that in general
pulumi plugin install
should always let you manually download any plugin you need. If you see any errors from that command - feel free to open an issue with details. That said - unless you manually delete the plugins, you generally shouldn't have to worry about this, as
npm install
will take care of acquiring any plugins you need.