Hi - Just to clarify, your examples mention "cache keys" - can you confirm these keys are stored external to the action code/container? I guess the behavior you are after is that a cache is populated the first time a particular version of the action is invoked, and the action is responsible for populating the cache? This will require it to be ok that the cache is overwritten by multiple concurrent action invocations - is that ok? Otherwise some external coordination will be required.
Thanks Tyson On 12/3/19, 1:56 AM, "Christophe Jelger" <[email protected]> wrote: Hello, I just joined the dev list after opened https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fopenwhisk%2Fpull%2F4761&data=02%7C01%7Ctnorris%40adobe.com%7Cf6bbce97138840d6d3d808d777d713e2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637109637950585977&sdata=NpAWRBdQiBdA%2BUc6YED%2BppFJnVQT31OU4YXF6Dg%2FRn0%3D&reserved=0 : it adds OW_ACTION_VERSION to the execution environment. I was asked by Rodric to send this email to the list because this change will require extra changes in the runtime repos for tests (see his comment in the PR). Since I just joined the list and have until now only been an active user of OpenWhisk, I don’t know what the process is to do that next. Any hint is appreciated. BR, Christophe -- Christophe Jelger | AEM Commerce Developer Adobe Research Schweiz AG +41 (0)61 226 5792
