any ideas please?
# general
b
any ideas please?
c
@sparse-insurance-40223 this is saying that the azure plugin failed to install into
~/.pulumi
(e.g.), you might be able to fix it by blowing away
node_modules
and then re-installing all your dependencies
Oh, apparently we made the plugin loader more strict cc @incalculable-sundown-82514
i
Yes, currently tracking https://github.com/pulumi/pulumi-azure/issues/200. To get unblocked you can 1) set the environment variable
PULUMI_ENABLE_LEGACY_PLUGIN_SEARCH=1
to fall back to the old behavior and 2) run
pulumi plugin install
with that environment variable set to install any plugins that may be missing. I apologize for the trouble, we’re working on improving this experience as we speak.
(My current theory is that we have accidentally regressed the automatic plugin installation that Pulumi normally does)
f
I have the same issue - running
yarn install
on jenkins, this creates node_modules, but ~/.pulumi directory is not created, and plugins are not installed This worked before - not sure what changed
@incalculable-sundown-82514 The work around you suggested does not seem to work:
Copy code
$ export PULUMI_ENABLE_LEGACY_PLUGIN_SEARCH=1
$ yarn install --frozen-lockfile
$ pulumi plugin install
[resource plugin aws-0.17.0] installing
[resource plugin kubernetes-0.21.0] installing
$ pulumi up --skip-preview --yes
Updating (TradeRev/test1):
Permalink: <https://app.pulumi.com/[snip]>
error: could not load plugin for aws provider 'urn:pulumi:test1::retail-api::pulumi:providers:aws::default': no resource plugin 'aws-v0.17.1' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource aws v0.17.1`
i
@faint-vegetable-61837 thanks for the report, can you run
pulumi plugin install --verbose
and
pulumi plugin ls
and post their outputs?
Can you also post the version of yarn you’re using?