<@UB89GSWCF> this introduces concurrent vendoring ...
# atmos-dev
e
@Andriy Knysh (Cloud Posse) this introduces concurrent vendoring the way we do with toolchain installation. Many users have extensive vendor configs and this should provide a nice speedup. cc @PePe Amengual github.com/cloudposse/atmos/pull/3169
❤️ 1
👀 1
merged 1
p
how cache evictions are calculated?
e
This refers to the GitHub Cache.
E.g. a folder that is stored as an artifact
p
this might be a more broader question: but I was wondering how atmos decides that the artifacts versioned are cached and evicted from the cache
e
There are many caches in atmos
There's the in memory cache, which is used to cache results for lookups; the lifecycle is just to the end of the process
There's the modules/provider cache which is implemented as a registry proxy; It has a max TTL you configure.
There's the "native CI caching" which is where atmos can work together with the GitHub artifact cache; evicition there is governed by your Github policy typically based on cache size, and oldest items are evicted to free up space
👍🏽 1