No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

it sounds like automatic plugin acquisition isn't working for that package, you can work around it by doing `pulumi plugin install resource eks &lt;version&gt;`

I was trying to avoid doing that :disappointed: I was hoping i did something wrong.
This looks like a really rough solution. I can't imagine this being manageable in a ci/cd where it would be easy to forget to update the version in the workflow file.
Should I report the bug somewhere ? <@UCWG26BH7>

• is the eks package in your `package.json` ?
• can you share your npm install log?

if by `eks package` you mean `@pulumi/eks` then yes. I linked the version in the original message. It also has the correct version in `package-lock`.
Install log in CI (without the Downloading bits)
```&gt; @pulumi/aws@4.25.0 install /home/runner/work/devops/devops/node_modules/@pulumi/aws
&gt; node scripts/install-pulumi-plugin.js resource aws v4.25.0

[resource plugin aws-4.25.0] installing


&gt; @pulumi/docker@3.1.0 install /home/runner/work/devops/devops/node_modules/@pulumi/docker
&gt; node scripts/install-pulumi-plugin.js resource docker v3.1.0

[resource plugin docker-3.1.0] installing

&gt; @pulumi/kubernetes@3.8.3 install /home/runner/work/devops/devops/node_modules/@pulumi/kubernetes
&gt; node scripts/install-pulumi-plugin.js resource kubernetes v3.8.3

[resource plugin kubernetes-3.8.3] installing

&gt; @pulumi/cloudflare@4.0.0 install /home/runner/work/devops/devops/node_modules/@pulumi/cloudflare
&gt; node scripts/install-pulumi-plugin.js resource cloudflare v4.0.0

[resource plugin cloudflare-4.0.0] installing

&gt; @pulumi/random@4.3.1 install /home/runner/work/devops/devops/node_modules/@pulumi/random
&gt; node scripts/install-pulumi-plugin.js resource random v4.3.1

[resource plugin random-4.3.1] installing


&gt; @pulumi/tls@4.0.0 install /home/runner/work/devops/devops/node_modules/@pulumi/tls
&gt; node scripts/install-pulumi-plugin.js resource tls v4.0.0

[resource plugin tls-4.0.0] installing```
These are the only ones relevant to pulumi. It just seems like eks is completely ignored

Just to mention: manually installing the plugin in the CI as a separate step does indeed work, but I have a feelign it should be picked up from `package.json` like the rest of plugins

<@UCWG26BH7> so what do you think about this ? Is this considered a bug ?

I'm honestly not sure, please feel free to file an issue