Carlos Santana

@amye Could you mark the following done. - [ ] Artwork: Submit a pull request to https://github.com/cncf/artwork with your artwork The logo were added https://github.com/cncf/artwork/tree/master/projects/knative

Have a copy and support all options as kubectl create secret including registry creds. alias “kn secret create”=”kubectl create secret” alias “kn create”=”kubectl create cm”

New domain name for the toolkit https://cloudnativetoolkit.dev

We found workaround using `--generate -d ./index.Dockerfile` then the next step in tekton using the Dockerfile with buildah or podman in a tekton task work to build the catalog image...

@trieloff can you open an issue in main repo https://github.com/apache/incubator-openwhisk for an enhancement request? The work needs to be done in the controller and invoker as phase1, they need to...

But controller and invoker already treats tgz as binary ? Also we need to handle the UX either documenting which runtimes can handle the tgz and which ones not while...

If controller/invoker treats binary transparently today leaving it to the runtime then I agree there is no need for changes in main/core

I don’t follow your comment Your saying to publish the proxy code as an external library on npm? Actions don’t need this as it’s a proxy that it’s already present...

Ok thanks both @ieb and @alexkli for the explanation. I have some more questions. Could share a hello work example on how a developer would configure its package.json and configure...

codecov is very good, we have in the clien-js repo 99% https://github.com/apache/incubator-openwhisk-client-js We also have a code style at 99%