hey all! wondering if i could get some debugging h...
# pulumi-cloud
s
hey all! wondering if i could get some debugging help. all of a sudden, my deployments (triggered via Github PRs) are failing at
npm install
time. we haven't changed anything that should be affecting this. is there a good way to debug this? (eg, manually performing the install and doing some basic things like
ls
and `cat`ing files)
happy to provide any more background around repo structure and stuff, but it's fairly vanilla and has been working for ~2 weeks without fail until today
l
Is your packages.json in the expected directory? It looks like the installation is happening but not in the right directory.
s
@little-cartoon-10569 we're using a monorepo structure like this (no
package.json
at the stack level)
Copy code
|- package.json|
|- infrastructure
   |- eks-cluster
      |- Pulumi.yaml
      |- index.ts
l
npm install
creates node_modules at the same level as package.json. If you have no package.json, then you'll have this error, I guess?
Let me check on my computer
s
yea, but
pulumi
seems to handle this just fine. locally, if i do an
npm install
from that
infrastructure/eks-cluster
directory, it creates
node_modules
next to the
package.json
(like you said), but
ulumi preview
works just fine
and the negative case is as expected too, removing
node_modules
causes
pulumi preview
to fail. so it's not like there's some other magic going on
l
Right, well it looks like Pulumi deployments is expecting a node_modules in /deployment/infrastructure/eks-cluster. If you can't arrange for one to be there, you may have to duplicate the deployment logic in your workflow
s
it's just weird that this structure has worked just fine for 2 weeks. all of a sudden, we made a trivial change and it stopped 😕