Has anyone have an idea why using the eks package to create

Question

Has anyone have an idea why using the eks package to create a cluster would give me this error I found <https github com pulumi pulumi issues 5578 issuecomment 709628863|something similar in an issue> but the workdir workaround is not helping GKE and AKS clusters work perfectly Am i missing a plugin I m installing `await ws installPlugin aws v3 22 0 ` but i cannot install an eks one so i gathered this is enough

billowy-army-68599 · Answer

it looks like your `package json` doesn t have ` pulumi pulumi` did you do an `npm install` in your pipeline

proud-pizza-80589 · Answer

It is and it is also in the local node modules we use yarn workspaces but all the pulumi packages and their dependencies are not hoisted

proud-pizza-80589 · Answer

and in the same run it can do GKE AKS Cloudflare and a bunch of k8s packages so it is specifically related to the eks package

proud-pizza-80589 · Answer

the folder it mentions just has the yaml files `Pulumi development eks europe pz yaml Pulumi yaml`

lemon-agent-27707 · Answer

I believe that you need to specifically set the workdir to the folder that has package json and `node modules`

lemon-agent-27707 · Answer

pulumi eks is trying to load something from your node modules ` pulumi pulumi cmd ` and failed

proud-pizza-80589 · Answer

I ve resolved the workdir to that folder but it keeps dying with the same error

proud-pizza-80589 · Answer

stackName settlemint development eks europe rtt projectName bpaas program AsyncFunction program workDir Users roderik Development bpaas launchpad packages launchpad api

proud-pizza-80589 · Answer

strike that i put it itno args not opts it runs

lemon-agent-27707 · Answer

Glad to hear you re unblocked Feel free to drop a note in that issue with the details of the issue you ran into or just give it a +1

proud-pizza-80589 · Answer

done i added a note because the workaround introduces another concurrency issue

lemon-agent-27707 · Answer

+1 wondering if using a temporary directory and sym linking node modules would work to get around polluting the directory with colliding stack yaml files <https github com pulumi pulumi issues 5578 issuecomment 755779509>