Dominic Kim

It's not easy to analyze the reason without information about your kubernetes environment. So generally a pod running on your k8s has access to the internet but the openwhisk pods...

@hunhoffe This is great! Thank you for your contribution.

> I could create an issue for it so it is not forgotten if that's acceptable. I am ok with this.

I formatted your description for better readability. It seems it complains about `invokerHealthTestAction.` How did you initialize CouchDB?

I would look into the DB. It generally looks like this. ```json { "_id": "whisk.system/invokerHealthTestAction0", "_rev": "187-cb37241d627e51fc27ba74690ab13fd2", "annotations": [], "entityType": "action", "exec": { "kind": "nodejs:10", "code": "function main(params) { return...

+1 on this

Any updates on this issue? This feature is provided in the serverless framework and we should support this at least for nodejs I think to attract more users.

oh I found this. https://medium.com/openwhisk/whisk-deploy-zip-actions-with-include-exclude-30ba6d96ad8b Then what is the relationship with this PR?

self answering to my question. It is to support the `npm install` step.

Yes, this is an old issue. When you create a trigger with `wsk`, seemingly it just creates the trigger, but it actually creates a trigger and executes a feed action...