great-sunset-35512/06/2023, 1:52 PM
Ideally I'd like to be able to make a list of required plugins before downloading.
limited-rainbow-5165012/06/2023, 3:46 PM
points to such a cache folder, it will fill at first run and Pulumi will pick up matching plugin versions afterwards and no longer download them.
great-sunset-35512/06/2023, 4:54 PM
is not the problem.
What I am not sure about is that if Github can incrementally build this cache from multiple jobs.
my projects run in parallel and they often have slightly different deps.
I am not sure what to use as a cache key.
On a small scale, I just ran
for each project in a separate job.
-> parallel [
build cache (pulumi install)
the problem with this approach that
pulumi up <project>
step may take ages to complete.
Ultimately the question is, what to choose as a
In my simple monorepo case I went with
but if I use this in parallel job it will probably override the cache
dry-keyboard-9479512/06/2023, 5:17 PM
, then save cache with a key made up of all lockfiles.
The job should run periodically, and whenever the lockfiles change.
Then your individual jobs can load the central cache.
great-sunset-35512/06/2023, 7:15 PM
dry-keyboard-9479512/06/2023, 7:21 PM
great-sunset-35512/07/2023, 5:40 AM
app project = workflow consumer
dry-keyboard-9479512/07/2023, 7:28 AM
great-sunset-35512/07/2023, 7:36 AM
dry-keyboard-9479512/07/2023, 7:37 AM
great-sunset-35512/07/2023, 7:45 AM