Currently, there is no way to deploy a composition using the aio cli. Instead, we need to manually install the openwhisk-composer package, set up environment variables (or a .wskprops file) and deploy manually.
What I'd like to happen is to be able to reference a composition's JS file in the manifest, and have it deployed with the rest of the application.
- Define the composition in a JS file somewhere (e.g. a
compositions folder)
- Declare the composition in
app.config.yaml - suggested format:
runtimeManifest:
packages:
myPackage:
actions:
...
sequences:
...
compositions:
compositionA:
definition: src/compositions/compositionA.js
web: 'yes'
annotations:
require-adobe-auth: true
Being able to deploy all actions, sequences and compositions via a single command would be highly preferable, compared to the current situation, where a composition has to be deployed separately (and then updated to be web-accessible, etc. if desired)
Currently, there is no way to deploy a composition using the aio cli. Instead, we need to manually install the
openwhisk-composerpackage, set up environment variables (or a.wskpropsfile) and deploy manually.What I'd like to happen is to be able to reference a composition's JS file in the manifest, and have it deployed with the rest of the application.
compositionsfolder)app.config.yaml- suggested format:Being able to deploy all actions, sequences and compositions via a single command would be highly preferable, compared to the current situation, where a composition has to be deployed separately (and then updated to be web-accessible, etc. if desired)