You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a monolithic repository with 10s of environments. Grouping provider lock updates as a grouped PR therefore makes sense. However, these can time out since dependabot is downloading the providers every time for each directory with a providers lock (even though in many cases they are the same provider at the same version).
Could it make sense to enable the provider plugin cache by setting the TF_PLUGIN_CACHE_DIR environment variable, and then passing -enable-plugin-cache to terraform providers lock to optimise grouped updates?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We have a monolithic repository with 10s of environments. Grouping provider lock updates as a grouped PR therefore makes sense. However, these can time out since dependabot is downloading the providers every time for each directory with a providers lock (even though in many cases they are the same provider at the same version).
Could it make sense to enable the provider plugin cache by setting the
TF_PLUGIN_CACHE_DIRenvironment variable, and then passing-enable-plugin-cachetoterraform providers lockto optimise grouped updates?Beta Was this translation helpful? Give feedback.
All reactions