Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Deploy compositions as part of aio app deploy

Open
  • Is something wrong?
#890 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
cli, cloud

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.

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:
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)

Dominant language
JavaScript
Stars
28
Forks
41
Avg merge
1d 13h
Merged PRs (30d)
6

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from adobe/aio-cli-plugin-app

All issues in adobe/aio-cli-plugin-app

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.