The runtime manifest upstream changed the default for node actions from 6 to 10 (note that the former reaches end of life in april). This exposed a weakness and some technical debt in the catalog installation since node 10 does not have many packages and some of the actions depend on libraries to work correctly.
For the short term fix to restore the catalog installation, one has to adapt the utils.sh script to accept a new parameter for the action kind... or since this PR looks ready https://github.com/apache/incubator-openwhisk-catalog/pull/268 we should move to wskdeploy for the installation and make sure that manifest pins the runtime for now. Will this latter approach work with the latest wsk binary (@pritidesai)?
As a second fix, we have adjust the installation to work with newer runtime kinds --- this is either by figuring out which dependencies to add to our runtimes, or to automate the creation of zipped actions as things stand today.
The runtime manifest upstream changed the default for node actions from 6 to 10 (note that the former reaches end of life in april). This exposed a weakness and some technical debt in the catalog installation since node 10 does not have many packages and some of the actions depend on libraries to work correctly.
For the short term fix to restore the catalog installation, one has to adapt the utils.sh script to accept a new parameter for the action kind... or since this PR looks ready https://github.com/apache/incubator-openwhisk-catalog/pull/268 we should move to wskdeploy for the installation and make sure that manifest pins the runtime for now. Will this latter approach work with the latest
wskbinary (@pritidesai)?As a second fix, we have adjust the installation to work with newer runtime kinds --- this is either by figuring out which dependencies to add to our runtimes, or to automate the creation of zipped actions as things stand today.