adobe / adobe/aio-cli-plugin-app
Deploy compositions as part of aio app deploy
- Dominant language
- JavaScript
- Stars
- 28
- Forks
- 41
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 3
Description
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:
```yaml
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)
Contributor guide
Research direction
Start by reading the proposed app.config.yaml runtimeManifest format and the referenced composition JS files. Compare the requested composition fields with the existing action and sequence deployment behavior; done means aio app deploy handles compositions alongside those resources, including the requested web setting and annotations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100