"Sven Lange-Last" <sven.lange-l...@de.ibm.com> wrote on 09/16/2019 01:51:11
PM:
>
> I opened PR #4627 to improve documentation. Said PR also adds
> "documentation" to the pre-defined Openwhisk runtime manifest files to
> make developers aware that renaming or removing runtime kinds can cause
> problems.
>
Hi Sven,
This is useful to write down. It should be an item in a best
practice guideline for operators of OpenWhisk deployments.
I think the community assumption is that all downstream OpenWhisk
operators are maintaining their own internal versions of runtimes.json
precisely because they need absolute control over their set of supported
runtimes. And because they don't actually use the default runtimes.json,
they should be insulated and able to consume all schema-preserving upstream
changes related to runtimes.json at their own pace.
It is a good point that the community could have made it more obvious
to downstream operators that there was a change they needed to consume
carefully in PR#4390 by leaving behind a deprecated kind for some period of
time.
--dave
