Hey all! Cool that you have this slack! I'm exploring Pulumi for our org and have set up a few stacks and started making a Github Action to run

pulumi up

and deploy the stack to production. The first time Pulumi runs in CI it seems to take 5-6min before even beginning to run the stack (we have a log right at the start) and I was hoping that there would be some way to cache the output of whatever initialization work is happening? We're using Go to define our stacks and I've downloaded dependencies ahead of time and cached the Pulumi plugins... we don't have hardly any encrypted values in the config, so I don't think it's that either...

The delay happens the first time but not thereafter? Sounds like it's already caching things nicely.

Yes, but I need to take the output of whatever it's caching so that I can restore it between jobs/runs

I'm not sure that you can cache it between jobs without external intervention, like creating a git repository that contains ~/.pulumi, then cloning that repo and putting it in ~/.pulumi for each job. However you should be able to cache it between runs easily (assuming you're not already doing this.. it looks like you are since only the first run is slower?). Use GitHub's built-in support for caching (see https://github.com/actions/cache), and the directory to cache is ~/.pulumi. It looks like this will (soon?) be built into the Pulumi GitHub Action, you can vote on that here: https://github.com/pulumi/actions/issues/804

Thanks for the response! yeah I tried caching everything in ~/.pulumi (including plugins) and it still takes 5 minutes after restoring the cache... the plugins weren't the long pole it seems like, there must be something else happening? I get the log

@ Updating...

with then a

.

every ~second thereafter Also got this log towards the beginning:

/usr/local/bin/pulumi version
v3.173.0
warning: A new version of Pulumi is available. To upgrade from version '3.173.0' to '3.175.0', visit <https://pulumi.com/docs/install/> for manual instructions and release notes.
Pulumi version 3.173.0 is already installed on this machine. Skipping download

is there any chance the action might be auto updating the Pulumi CLI? I've been looking at the CLI source code and that's one of the only things I see that runs a check on each command?