The current recommendation is to use something like

m2-{{ checksum "pom.xml" }}

This really doesn't work because our pom.xml file changes with every build. The cache exists, but does no good. It is never re-used. We'd like to be able to periodically flush our cache. Either with a workflow trigger (weekly, monthly, etc) or by manually setting a env var in our build yaml/script. We could key the cache of a parent pom version, or just use the year/month string. Many different option, but currently the

{{ .Environment.variableName }}

syntax does not support user set env vars. We could put it in a context, but this requires manual intervention. We'd like the cache to just magically clear on a regular basis.

CCI-I-658