nirs
commented
1 month ago This is fixed by #1389 - with this you can never have cache older than 2 days, and if you want you can set a cron job to update your cache transparently.
We can add an option to disable the cache completely which is useful for developers using a fast internet connection, and do not care about rate github outages.
Following a debugging session with @nirs we discovered I was using some cached clusteraddon manifests that date back several months, and had a bug in them:
My proposal is to have the drenv not cache by default, and have caching be an opt-in feature. I am not sure if that's reasonable to ask but I was surprised to learn of the existence of this cache in my case