https://pulumi.com logo
Join Slack
Powered by
This message was deleted.
# pulumiverse
s
This message was deleted.
l
We have an open issue on this, but weren’t able to get to a reproducible case. https://github.com/pulumi/pulumi/issues/10882
h
is there another issue for 
pulumi plugin install
not supporting 
pluginDownloadURL
?
i tried searching but i came up empty
e
pulumi plugin install
can't work out 
pluginDownloadURL
automatically, it needs the 
--server
option. But I only know of two real issues around plugin downloads: 1. The above issue where we lose track of the download url when providers are restored from state 2. We don't retry github 403 rate limit errors
g
Thanks @echoing-dinner-19531 I suspect this is caused by 
1.
because I worked around 
2.
by caching plugins directory and GITHUB_TOKEN
h
1. The above issue where we lose track of the download url when providers are restored from state
the issue for us this time was that an older version of the provider was specified in the state from previous runs and that version was downloaded correctly, but the new version was not.
e
Odd I haven't seen that failure mode before
h
looks like in our case the problem is that we are sharing a 
node_modules
cache between our github workflows, but not the 
pulumi plugin
cache. So in our (code) build/test step we install cache 
node_modules
-> when we run the pulumi workflow the npm module is already installed -> no new plugin download from yarn install -> crash at runtime
e
ah ok, does it not try to download it at runtime when it sees that version missing?
h
it does, but not with 
pluginDownloadURL
e
Oh interesting, if you get any logs of that do send them our way
h
Copy code
Run pulumi/actions@v4
Configured range: ^3
Matched version: v3.55.0
Install destination is /home/runner/.pulumi
Successfully deleted pre-existing /home/runner/.pulumi/bin
/usr/bin/tar xz --warning=no-unknown-keyword --overwrite -C /home/runner/.pulumi -f /home/runner/work/_temp/7b6bed36-6bbd-44ed-98a9-ec9aaf662737
Logging into the Pulumi Service backend.
pulumi preview on orgname/stackname
  Error: code: -2
   stdout: 
   stderr: Command failed with exit code 255: pulumi preview --diff --parallel 2147483647 --exec-agent pulumi/actions@v4 --color always --exec-kind auto.local --event-log /tmp/automation-logs-preview-o7seSM/eventlog.txt --stack bluecodecom/bcx-shared --non-interactive
  [resource plugin sentry-0.0.4] installing
  error: Could not automatically download and install resource plugin 'pulumi-resource-sentry' at version v0.0.8, install the plugin using `pulumi plugin install resource sentry v0.0.8`.
  Underlying error: error downloading plugin sentry to file: failed to download plugin: sentry-0.0.8: 403 HTTP error fetching plugin from <https://get.pulumi.com/releases/plugins/pulumi-resource-sentry-v0.0.8-linux-amd64.tar.gz>
as you can see the old version of the plugin 
v0.0.4
, which is referenced from the stack is downloaded correctly
but the new version 
v0.0.8
from 
package.json
fails
e
ah ok, another one to look into then
b
On my side from yesterday I’m unable to download and install the sentry plugin. The issue is 
401 HTTP error fetching plugin from <https://api.github.com/repos/pulumiverse/pulumi-sentry/releases/tags/v0.0.8>
This happens whatever workflow I use, using automation api, try to install it using the CLI on my dev machine, every where.
l
@brash-hairdresser-60389 can you verify whether you didn’t hit the Github API rate limits? 
curl -i <https://api.github.com/rate_limit>
To increase these limits, make sure that you have a valid 
GITHUB_TOKEN
set. Pulumi will (when defined) send this along on any plugin download request to make it an authenticated request.
12 Views
Open in Slack
PreviousNext
Powered by