#cache volumes and terraform init
1 messages · Page 1 of 1 (latest)
It depends how you have your pipeline setup. If you have multiple terraform inits within the scope of one CI run, and they all use the same volume, I'd probably give them each their own volume. If you just have one init in a run but you're worried about concurrent CI runs, Dagger volume caches are safe for this case because each init will have it's own copy of the volume
in addition to what Kyle is mentioning, if you're planning to share the same cache volume across multiple Dagger pipelines, you can set the shared mode in the WithMountedCache op which will allow safe concurrent access to it: https://pkg.go.dev/dagger.io/dagger#CacheSharingMode
Ooh, how does cache sharing mode work?
Oh, that's super cool!