I found a gap in the above example where `common/utility.js` is under
`actions/` so when its specified as is under `include` section,
`common/utility.js` can not be found. Here is the directory structure with
`manifest.yaml`:
```
ls -1 ./
manifest.yaml
actions
ls -1 actions/common/
utility.js
ls -1 actions/action1/
action1.js
package.json
ls -1 actions/action2/
action2.js
package.json
ls -1 actions/action3/
action3.js
package.json
```
Here is the updated manifest:
```
packages:
myPackage:
actions:
action1:
function: actions/action1
runtime: nodejs:6
include:
- actions/common/utility.js
action2:
function: actions/action2
runtime: nodejs:6
include:
- actions/common/utility.js
action3:
function: actions/action3
runtime: nodejs:6
include:
- actions/common/utility.js
```
Also, zipped actions must contain either package.json or index.js at the root
which means `actions/common/utility.js` has to be moved under
`actions/action1`. Now, either we move **all** files listed under `include`
under root dir specified at the function level or we add a `source` and
`destination` terminology in the manifest.
[ Full content available at:
https://github.com/apache/incubator-openwhisk-wskdeploy/issues/969 ]
This message was relayed via gitbox.apache.org for [email protected]
