magnificent-pizza-54661
12/08/2022, 2:00 AMclever-sunset-76585
12/08/2022, 2:07 AMmagnificent-pizza-54661
12/08/2022, 2:16 AMclever-sunset-76585
12/08/2022, 2:43 AMmagnificent-pizza-54661
12/08/2022, 2:50 AMerror: no resource plugin 'pulumi-resource-aws' found in the workspace at version v5.23.0 or on your $PATH, install the plugin using `pulumi plugin install resource aws v5.23.0`
This is that pulumi is in the $PATH otherwise the cli wouldn't have worked at all.
It does seem to me like it's more of a CI issue then a Pulumi issue though.clever-sunset-76585
12/08/2022, 2:54 AMnpm ci
or yarn install
(depending on your choice of package manager) before running Pulumi?
EDIT: ...in CImagnificent-pizza-54661
12/08/2022, 2:55 AMcurl -fsSL <https://get.pulumi.com> | sh -s -- --version 3.37.1
yarn install --force --frozen-lockfile
export PATH=\$HOME/.pulumi/bin:\$PATH
yarn preview
Where the preview script is what calls the automation apiclever-sunset-76585
12/08/2022, 2:59 AM~/.pulumi/plugins
. Also what is your CI build agent's architecture?magnificent-pizza-54661
12/08/2022, 3:01 AMclever-sunset-76585
12/08/2022, 3:07 AMyarn
prevents the installation of the Pulumi plugin somehow? Or maybe the way yarn
runs the command doesn't have the user HOME
configured correctly in CI? Try printing the contents of $HOME/.pulumi/plugins
before your yarn preview
and check that plugins for the providers that your project depends on have been installed. You could also alternatively run pulumi plugin ls
.magnificent-pizza-54661
12/08/2022, 3:10 AMclever-sunset-76585
12/08/2022, 3:12 AM.pulumi/plugins
dir actually does have the provider plugins. At least then you can definitely narrow it down to some yarn
or Volta
weirdness.magnificent-pizza-54661
12/08/2022, 3:14 AMclever-sunset-76585
12/08/2022, 3:40 AM