Please consider using several partial keys in restore_cache

[circleci-public]

Please consider using several partial keys in restore_cache

[julienw]

I think it's quite easy to support the partial keys, what's more difficult is to make it configurable :-) But not sure there's a downside in having it all the time.

[patatepartie]

I would just add the {{ arch }} template, inside the key, as it's recommended in some parts of the docs and would help people with builds on different architectures, at no cost for those who don't.

[KyleTryon]

Have a solution prepared: #83

[KyleTryon]

Yes, unfortunately, because caching is achieved via CircleCI config and is not "programable", it would be difficult to support multiple cache keys via an orb. The addition of {{ arch }} however should assist some (I can't think of any downsides).

In semi relation, I have also opened this feature request for CircleCI to allow more programmatic access to cache and artifacts. Please feel free to vote here: https://ideas.circleci.com/api-feature-requests/p/programmatic-cache-and-artifact-access

[Kurt-von-Laven]

Yeah, sorry, could you clarify that point, @KyleTryon? I don't see why this feature request would imply any special programmatic access to caches. The proposal as I understand it is to apply partial cache restoration as recommended by CircleCI. Having partial cache restoration all the time would break NPM users without a lock file as well as NPM users on version 4-. That being said, I don't personally feel there is a need for this feature being configurable at least in its first iteration since the command can inspect the presence of a lock file and npm --version and branch accordingly.

[KyleTryon]

It looks like we could enable this as non-configurable.