@adobe/aio-cli
Adobe I/O Extensible CLI ******* ******* ****** ****** ***** ***** **** * **** *** *** *** ** ***** ** * ** *
Last updated 9 days ago by purplecabbage .
Apache-2.0 · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install @adobe/aio-cli 
SYNC missed versions from official npm registry.

oclif Version Downloads/week Build Status License Greenkeeper badge Codecov Coverage

aio-cli

Adobe I/O Extensible CLI

aio cli health

Health badges for the aio-cli and its plugins and modules

Module Version Downloads Build Status Coverage Issues Pull Requests
@adobe/aio-cli Version Downloads/week Build Status Codecov Coverage Github Issues Github Pull Requests
@adobe/aio-cli-plugin-config Version Downloads/week Build Status Codecov Coverage Github Issues Github Pull Requests
@adobe/aio-cli-plugin-jwt-auth Version Downloads/week Build Status Codecov Coverage Github Issues Github Pull Requests
@adobe/aio-cli-plugin-console Version Downloads/week Build Status Codecov Coverage Github Issues Github Pull Requests
@adobe/aio-cli-plugin-runtime Version Downloads/week Build Status Codecov Coverage Github Issues Github Pull Requests
@adobe/aio-cli-plugin-app Version Downloads/week Build Status Codecov Coverage Github Issues Github Pull Requests
@adobe/aio-cli-plugin-auth Version Downloads/week Build Status Codecov Coverage Github Issues Github Pull Requests
@adobe/aio-cli-plugin-certificate Version Downloads/week Build Status Codecov Coverage Github Issues Github Pull Requests
@adobe/aio-cli-plugin-info Version Downloads/week Build Status Codecov Coverage Github Issues Github Pull Requests
@adobe/generator-aio-app Version Downloads/week Build Status Codecov Coverage Github Issues Github Pull Requests

Getting started

Pre-requisites

Additional tools for debugging

Installing CLI tools

Firstly you need to install Adobe I/O CLI. It comes with all-batteries-included tools for building apps.

npm install -g @adobe/aio-cli

Bootstrapping an application

In order to create your first application, use the following command:

aio app init <app-name>

You will be prompted with a few questions about how you want your app to have:

  1. Select app features to enable:
  • Actions: Deploy Runtime actions: adding the boilerplate for backend serverless actions on I/O Runtime
  • Web Assets: Deploy hosted static assets: adding the boilerplate for frontend react app and static assets

You can select either of the options, or both to have a full app for both back and frontend.

  1. Select one or more sample actions to be generated along with the new app:
  • Adobe Target: including dependencies and examples of accessing the Adobe Target API
  • Adobe Analytics: including dependencies and examples of accessing the Adobe Analytics API
  • Adobe Campaign Standard: including dependencies and examples of accessing the Adobe Campaign Standard (ACS) API
  • Generic: a generic application with hello world flow
  1. Define the names of sample actions (by keeping the defaults or specifying other names). The new app is then generated, and npm dependencies are getting installed.

  2. Open the project in VSCode, by entering the command code <app-name>, or opening VSCode -> Open... -> select app folder.

  3. Open .env file, add your I/O Runtime credentials in the AIO_RUNTIME_XXX variables, and uncomment them.

Main components of the App

  • actions: backend source code for all serverless actions.
  • web-src: frontend source code such as html templates, react components, JS, CSS.
  • test: including unit tests and integration tests.
  • manifest.yml: definition of I/O Runtime actions being deployed with the app
  • package.json: project definition and metadata
  • .env: containing environment variables that are useful for the app, e.g. I/O Runtime credentials and Adobe Product API tenant specifics (API key, secrets, etc.)
  • .aio: containing config variables that are useful for the AIO CLI to facilitate the app, e.g. authentication strategy (JWT / OAuth)

Local development

Running the application

Before running the application locally for the first time, make sure that the required docker images are existing in the local machine.

docker pull openwhisk/action-nodejs-v10:latest
docker pull adobeapiplatform/adobe-action-nodejs-v10:3.0.21

Note: Developers on Windows machines should make sure that they are using Linux containers for the images above. The steps to switch to Linux containers are described in the Docker for Windows documentation.

To run the application locally, use the following command:

aio app run

This will deploy the actions to Adobe I/O Runtime, while running the UI part on the local machine. The app is accessible on the browser at localhost:9080 (by default, but the port is configurable).

To have the application running completely locally, which means the actions run on a local deployment of (standalone) OpenWhisk, add the --local flag to the above run command. It will make actions accessible at localhost:3233/api/v1/web/guest/<app-name>-<version>/<action>.

Debugging the application

Make sure that local dev environment is running, either with or without --local.

An example debugging flow:

  • Set a breakpoint in your code
  • Go to debugger mode in VSCode
  • Select Web and actions profile for debugging
  • Click on Run, the debugger will stop at the breakpoint and you can inspect your app execution

If the local development is run without --local flag, you debug the actions running directly on Adobe I/O Runtime. When the --local flag is set, the actions are debugged in the standalone OpenWhisk instance running locally. More about this can be found on the wskdebug docs.

Getting logs

To see logs of your app, use the command aio app logs. By default, only the logs of the latest activation is fetched. If you want to see a more extensive list of logs, use the --limit flag to define the number of recent activations to be fetched.

Publishing the application

Once the application is in a good shape, it could be deployed to a dev environment. This is achievable with a single command.

aio app deploy

This will invoke:

  • The actions defined in manifest.yml being updated on Adobe I/O Runtime
  • The frontend built files and assets being uploaded to our CDN.

The deployment outputs a URL of the app which is publicly accessible on Adobe Experience Cloud (ExC Shell). The URL format is https://experience.adobe.com/?devMode=true#/myapps/?localDevUrl=<your-app-url>.

The app could also be "unpublished" later with aio app undeploy.

References

https://www.adobe.io/apis/experienceplatform/runtime.html

Usage

$ npm install -g @adobe/aio-cli
$ aio COMMAND
running command...
$ aio (-v|--version|version)
@adobe/aio-cli/3.4.1 darwin-x64 node-v10.16.1
$ aio --help [COMMAND]
USAGE
  $ aio COMMAND
...

Commands

aio app

Create, run, test, and deploy Adobe I/O Apps

USAGE
  $ aio app

OPTIONS
  -v, --verbose  Verbose output
  --version      Show version

See code: @adobe/aio-cli-plugin-app

aio app:add

Add a new component to an existing Adobe I/O App

USAGE
  $ aio app:add

OPTIONS
  -v, --verbose  Verbose output
  --version      Show version

See code: @adobe/aio-cli-plugin-app

aio app:add:action

Add a new action

USAGE
  $ aio app:add:action

OPTIONS
  -v, --verbose   Verbose output
  -y, --yes       Skip questions, and use all default values
  --skip-install  Skip npm installation after files are created
  --version       Show version

See code: @adobe/aio-cli-plugin-app

aio app:add:auth

Add auth support

USAGE
  $ aio app:add:auth

OPTIONS
  -v, --verbose  Verbose output
  --version      Show version

See code: @adobe/aio-cli-plugin-app

aio app:add:ci

Add CI files

USAGE
  $ aio app:add:ci

OPTIONS
  -v, --verbose  Verbose output
  --version      Show version

See code: @adobe/aio-cli-plugin-app

aio app:add:web-assets

Add web assets support

USAGE
  $ aio app:add:web-assets

OPTIONS
  -v, --verbose   Verbose output
  -y, --yes       Skip questions, and use all default values
  --skip-install  Skip npm installation after files are created
  --version       Show version

See code: @adobe/aio-cli-plugin-app

aio app:create [PATH]

Create a new Adobe I/O App with default parameters

USAGE
  $ aio app:create [PATH]

ARGUMENTS
  PATH  [default: .] Path to the app directory

OPTIONS
  -i, --import=import  Import an Adobe I/O Developer Console configuration file
  -v, --verbose        Verbose output
  --version            Show version

See code: @adobe/aio-cli-plugin-app

aio app:delete

Delete a component from an existing Adobe I/O App

USAGE
  $ aio app:delete

OPTIONS
  -v, --verbose  Verbose output
  --version      Show version

See code: @adobe/aio-cli-plugin-app

aio app:delete:action [ACTION-NAME]

Delete an existing action

USAGE
  $ aio app:delete:action [ACTION-NAME]

ARGUMENTS
  ACTION-NAME  Action name to delete, if not specified you will choose from a list of actions

OPTIONS
  -v, --verbose  Verbose output
  -y, --yes      Skip questions, and use all default values
  --version      Show version

See code: @adobe/aio-cli-plugin-app

aio app:delete:ci

Delete existing CI files

USAGE
  $ aio app:delete:ci

OPTIONS
  -v, --verbose  Verbose output
  -y, --yes      Skip questions, and use all default values
  --version      Show version

See code: @adobe/aio-cli-plugin-app

aio app:delete:web-assets

Delete existing web assets

USAGE
  $ aio app:delete:web-assets

OPTIONS
  -v, --verbose  Verbose output
  -y, --yes      Skip questions, and use all default values
  --version      Show version

See code: @adobe/aio-cli-plugin-app

aio app:deploy

Build and deploy an Adobe I/O App

USAGE
  $ aio app:deploy

OPTIONS
  -a, --action=action  Deploy only a specific action, the flags can be specified multiple times
  -v, --verbose        Verbose output
  --skip-actions       Skip action build & deploy
  --skip-build         Skip build phase
  --skip-deploy        Skip deploy phase
  --skip-static        Skip build & deployment of static files
  --version            Show version

See code: @adobe/aio-cli-plugin-app

aio app:get-url [ACTION]

Get action URLs

USAGE
  $ aio app:get-url [ACTION]

OPTIONS
  -h, --hson     Output human readable json
  -j, --json     Output json
  -v, --verbose  Verbose output
  -y, --yml      Output yml
  --cdn          Display CDN based action URLs
  --version      Show version

See code: @adobe/aio-cli-plugin-app

aio app:init [PATH]

Create a new Adobe I/O App

USAGE
  $ aio app:init [PATH]

ARGUMENTS
  PATH  [default: .] Path to the app directory

OPTIONS
  -i, --import=import  Import an Adobe I/O Developer Console configuration file
  -s, --skip-install   Skip npm installation after files are created
  -v, --verbose        Verbose output
  -y, --yes            Skip questions, and use all default values
  --version            Show version

See code: @adobe/aio-cli-plugin-app

aio app:logs

Fetch logs for an Adobe I/O App

USAGE
  $ aio app:logs

OPTIONS
  -l, --limit=limit  [default: 1] Limit number of activations to fetch logs from
  -v, --verbose      Verbose output
  --version          Show version

See code: @adobe/aio-cli-plugin-app

aio app:run

Run an Adobe I/O App

USAGE
  $ aio app:run

OPTIONS
  -v, --verbose   Verbose output
  --local         run/debug actions locally
  --skip-actions  skip actions, only run the ui server
  --version       Show version

See code: @adobe/aio-cli-plugin-app

aio app:test

Run tests for an Adobe I/O App

USAGE
  $ aio app:test

OPTIONS
  -e, --e2e      runs e2e tests.
  -u, --unit     runs unit tests (default).
  -v, --verbose  Verbose output
  --version      Show version

See code: @adobe/aio-cli-plugin-app

aio app:undeploy

Undeploys an Adobe I/O App

USAGE
  $ aio app:undeploy

OPTIONS
  -v, --verbose   Verbose output
  --skip-actions  Skip action build & deploy
  --skip-static   Skip build & deployment of static files
  --version       Show version

See code: @adobe/aio-cli-plugin-app

aio app:use [CONFIG_FILE_PATH]

Import an Adobe I/O Developer Console configuration file

USAGE
  $ aio app:use [CONFIG_FILE_PATH]

ARGUMENTS
  CONFIG_FILE_PATH  path to an Adobe I/O Developer Console configuration file

OPTIONS
  -m, --merge      Merge any .aio and .env files during import of the Adobe I/O Developer Console configuration file
  -v, --verbose    Verbose output
  -w, --overwrite  Overwrite any .aio and .env files during import of the Adobe I/O Developer Console configuration file
  --version        Show version

See code: @adobe/aio-cli-plugin-app

aio auth

Adobe IMS commands to login and logout.

USAGE
  $ aio auth

DESCRIPTION
  The main commands are auth:login to get or create an access token and
  auth:logout to invalidate an access token and thus log out from Adobe IMS.

  Logging in and out is based on configuration of which there may be
  multiple. Each set of configuration properties, called an Adobe IMS context,
  can be individually addressed by a label.

  Configuration for the Adobe IMS commands is stored in the "$ims"
  configuration property. The special property "$current" contains the
  label of the current configuration which can be set using the
  "aio auth ctx -s <label>" command.

  Each set of properties in a labeled Adobe IMS context configurations has
  configuration properties depending on the kind of access that is
  supported. The below example shows the configuration for OAuth2
  based (graphical SUSI) login.

  The "env" property is mandatory and designates the Adobe IMS environment
  used for authentication. Possible values are "stage" and "prod".
  If the property is missing or any other value, it defaults to "stage".

  All commands allow their normal output to be formatted in either
  HJSON (default), JSON, or YAML.

EXAMPLE
  {
       $ims: {
         postman: {
           env: "stage",
           callback_url: "https://callback.example.com",
           client_id: "example.com-client-id",
           client_secret: "XXXXXXXX",
           scope: "openid AdobeID additional_info.projectedProductContext read_organizations",
           state: ""
         },
         $current: "postman"
       }
     }

See code: @adobe/aio-cli-plugin-auth

aio auth:ctx

Manage Adobe IMS contexts.

USAGE
  $ aio auth:ctx

OPTIONS
  -c, --ctx=ctx  Name of the Adobe IMS context to use. Default is the current Adobe IMS context
  -g, --global   global config
  -l, --local    local config
  -s, --set=set  Sets the name of the current Adobe IMS context
  -v, --verbose  Verbose output
  --debug=debug  Debug level output
  --list         Names of the Adobe IMS contexts as an array
  --value        Prints named or current Adobe IMS context data

DESCRIPTION
  The following options exist for this command:

  * List the names of the configured Adobe IMS contexts
  * Print the name of the current Adobe IMS context
  * Set the name of the current Adobe IMS context
  * Print the configuration of the current or a named Adobe IMS context

  Currently it is not possible to update the Adobe Adobe IMS context configuration
  using this command. Use the "aio config" commands for this.
        e.g. aio config:set \$ims.your_context.your_context_key "your_context_value"

  Please note, that the Adobe Adobe IMS context labels starting with "$" are reserved
  and cannot be used as an Adobe IMS context name.

ALIASES
  $ aio ctx
  $ aio context

See code: @adobe/aio-cli-plugin-auth

aio auth:login

Log in with a certain Adobe IMS context and returns the access token.

USAGE
  $ aio auth:login

OPTIONS
  -b, --bare     print access token only
  -c, --ctx=ctx  Name of the Adobe IMS context to use. Default is the current Adobe IMS context
  -d, --decode   Decode and display access token data

  -f, --force    Force logging in. This causes a forced logout on the context first and makes sure to not use any cached
                 data when calling the plugin.

  -g, --global   global config

  -l, --local    local config

  -v, --verbose  Verbose output

  --debug=debug  Debug level output

DESCRIPTION
  If the Adobe IMS context already has a valid access token set (valid meaning
  at least 10 minutes before expiry), that token is returned.

  Otherwise, if the Adobe IMS context has a valid refresh token set (valid
  meaning at least 10 minutes before expiry) that refresh token is
  exchanged for an access token before returning the access token.

  Lastly, if the Adobe IMS context properties are supported by one of the
  Adobe IMS login plugins, that login plugin is called to guide through
  the IMS login process.

  The currently supported Adobe IMS login plugins are:

  * aio-lib-ims-jwt for JWT token based login supporting
     Adobe I/O Console service integrations.
  * aio-lib-ims-oauth for browser based OAuth2 login. This
     plugin will launch a Chromium browser to guide the user through the
     login process. The plugin itself will *never* see the user's
     password but only receive the authorization token after the
     user authenticated with Adobe IMS.

ALIASES
  $ aio login

See code: @adobe/aio-cli-plugin-auth

aio auth:logout

Log out the current or a named Adobe IMS context.

USAGE
  $ aio auth:logout

OPTIONS
  -c, --ctx=ctx  Name of the Adobe IMS context to use. Default is the current Adobe IMS context

  -f, --force    Invalidate the refresh token as well as all access tokens.
                 Otherwise only the access token is invalidated. For Adobe IMS
                 contexts not supporting refresh tokens, this flag has no
                 effect.

  -g, --global   global config

  -l, --local    local config

  -v, --verbose  Verbose output

  --debug=debug  Debug level output

DESCRIPTION
  This command can be called multiple times on the same Adobe IMS context with
  out causing any errors. The assumption is that after calling this command
  without an error, the Adobe IMS context's access and refresh tokens have been
  invalidated and removed from persistent storage. Repeatedly calling this
  command will just do nothing.

ALIASES
  $ aio logout

See code: @adobe/aio-cli-plugin-auth

aio autocomplete [SHELL]

display autocomplete installation instructions

USAGE
  $ aio autocomplete [SHELL]

ARGUMENTS
  SHELL  shell type

OPTIONS
  -r, --refresh-cache  Refresh cache (ignores displaying instructions)

EXAMPLES
  $ aio autocomplete
  $ aio autocomplete bash
  $ aio autocomplete zsh
  $ aio autocomplete --refresh-cache

See code: @oclif/plugin-autocomplete

aio certificate

Generate or verify a certificate for use with Adobe I/O

USAGE
  $ aio certificate

See code: @adobe/aio-cli-plugin-certificate

aio certificate:generate

Generate a new private/public key pair

USAGE
  $ aio certificate:generate

OPTIONS
  -c, --country=country            Country Name
  -l, --locality=locality          Locality, or city name

  -n, --name=name                  [default: selfsign.localhost] Common Name: typically a host domain name, like
                                   www.mysite.com

  -o, --organization=organization  Organization name

  -s, --state=state                State or Province

  -u, --unit=unit                  Organizational unit or department

  --days=days                      [default: 365] Number of days the certificate should be valid for. (Max 365)

  --keyout=keyout                  [default: private.key] file to send the key to

  --out=out                        [default: certificate_pub.crt] output file

DESCRIPTION
  Generate a self-signed certificate to enable https:// on localhost or signing jwt payloads for interacting with Adobe 
  services.

See code: @adobe/aio-cli-plugin-certificate

aio certificate:verify FILE

Verify a certificate for use with Adobe I/O

USAGE
  $ aio certificate:verify FILE

ARGUMENTS
  FILE  file path to certificate to verify

OPTIONS
  --days=days  +- is certificate valid in --days

DESCRIPTION
  Verifies that the certificate is valid, and/or will not expire in [--days] days from now.

See code: @adobe/aio-cli-plugin-certificate

aio config

list, get, set, delete, and edit persistent configuration data

USAGE
  $ aio config

OPTIONS
  -e, --env     environment variables
  -g, --global  global config
  -j, --json    output in json
  -l, --local   local config
  -y, --yaml    output in yaml
  --verbose     show all config values

ALIASES
  $ aio config:ls

EXAMPLES
  $ aio config:list
  $ aio config:get KEY
  $ aio config:set KEY VALUE
  $ aio config:delete KEY
  $ aio config:clear

See code: @adobe/aio-cli-plugin-config

aio config:clear

clears all persistent config values

USAGE
  $ aio config:clear

OPTIONS
  -f, --force   do not prompt for confirmation
  -g, --global  global config
  -l, --local   local config

See code: @adobe/aio-cli-plugin-config

aio config:delete KEYS...

deletes persistent config values

USAGE
  $ aio config:delete KEYS...

OPTIONS
  -g, --global  global config
  -l, --local   local config

ALIASES
  $ aio config:del
  $ aio config:rm

See code: @adobe/aio-cli-plugin-config

aio config:edit

edit config file

USAGE
  $ aio config:edit

OPTIONS
  -g, --global  global config
  -l, --local   local config

See code: @adobe/aio-cli-plugin-config

aio config:get KEY

gets a persistent config value

USAGE
  $ aio config:get KEY

OPTIONS
  -e, --env     environment variables
  -g, --global  global config
  -j, --json    output in json
  -l, --local   local config
  -y, --yaml    output in yaml

See code: @adobe/aio-cli-plugin-config

aio config:list

lists all persistent config values

USAGE
  $ aio config:list

OPTIONS
  -e, --env     environment variables
  -g, --global  global config
  -j, --json    output in json
  -l, --local   local config
  -y, --yaml    output in yaml
  --verbose     show all config values

ALIASES
  $ aio config:ls

See code: @adobe/aio-cli-plugin-config

aio config set key 'a value' # set key to 'a value'

sets a persistent config value

USAGE
  $ aio config set key 'a value'       # set key to 'a value'
  $ aio config set key -f value.json   # set key to the json found in the file value.json
  $ aio config set -j key < value.json # set key to the json found in the file value.json

OPTIONS
  -f, --file         value is a path to a file
  -g, --global       global config
  -i, --interactive  prompt for value
  -j, --json         value is json
  -l, --local        local config
  -y, --yaml         value is yaml

See code: @adobe/aio-cli-plugin-config

aio console

Console plugin for the Adobe I/O Console

USAGE
  $ aio console

OPTIONS
  --help  Show help

See code: @adobe/aio-cli-plugin-console

aio console:org

Manage your Adobe I/O Console Organizations

USAGE
  $ aio console:org

OPTIONS
  --help  Show help

See code: @adobe/aio-cli-plugin-console

aio console:org:list

List your Organizations

USAGE
  $ aio console:org:list

OPTIONS
  -j, --json  Output json
  -y, --yml   Output yml
  --help      Show help

ALIASES
  $ aio console:org:list

See code: @adobe/aio-cli-plugin-console

aio console:org:select ORGID

Select an Organization

USAGE
  $ aio console:org:select ORGID

ARGUMENTS
  ORGID  Adobe I/O Org Id

OPTIONS
  --help  Show help

ALIASES
  $ aio console:org:select
  $ aio console:org:sel

See code: @adobe/aio-cli-plugin-console

aio console:project

Manage your Adobe I/O Console Projects

USAGE
  $ aio console:project

OPTIONS
  --help  Show help

See code: @adobe/aio-cli-plugin-console

aio console:project:list

List your Projects for the selected Organization

USAGE
  $ aio console:project:list

OPTIONS
  -j, --json     Output json
  -y, --yml      Output yml
  --help         Show help
  --orgId=orgId  OrgID for listing projects

ALIASES
  $ aio console:project:ls

See code: @adobe/aio-cli-plugin-console

aio console:project:select PROJECTID

Select a Project for the selected Organization

USAGE
  $ aio console:project:select PROJECTID

ARGUMENTS
  PROJECTID  Adobe I/O Project Id

OPTIONS
  --help         Show help
  --orgId=orgId  OrgID of the project to select

ALIASES
  $ aio console:project:sel

See code: @adobe/aio-cli-plugin-console

aio console:where

Show the currently selected Organization, Project and Workspace

USAGE
  $ aio console:where

OPTIONS
  -j, --json  Output json
  -y, --yml   Output yml
  --help      Show help

ALIASES
  $ aio where

See code: @adobe/aio-cli-plugin-console

aio console:workspace

Manage your Adobe I/O Console Workspaces

USAGE
  $ aio console:workspace

OPTIONS
  --help  Show help

ALIASES
  $ aio console:ws

See code: @adobe/aio-cli-plugin-console

aio console:workspace:download [DESTINATION]

Downloads the configuration for the selected Workspace

USAGE
  $ aio console:workspace:download [DESTINATION]

ARGUMENTS
  DESTINATION  path where workspace configuration file will be saved

OPTIONS
  --help  Show help

ALIASES
  $ aio console:workspace:download
  $ aio console:workspace:dl
  $ aio console:ws:download
  $ aio console:ws:dl

See code: @adobe/aio-cli-plugin-console

aio console:workspace:list

List your Workspaces for your selected Project

USAGE
  $ aio console:workspace:list

OPTIONS
  -j, --json  Output json
  -y, --yml   Output yml
  --help      Show help

ALIASES
  $ aio console:workspace:list
  $ aio console:workspace:ls
  $ aio console:ws:list
  $ aio console:ws:ls

See code: @adobe/aio-cli-plugin-console

aio console:workspace:select WORKSPACEID

Select a Workspace for the selected Project

USAGE
  $ aio console:workspace:select WORKSPACEID

OPTIONS
  --help  Show help

ALIASES
  $ aio console:workspace:select
  $ aio console:workspace:sel
  $ aio console:ws:select
  $ aio console:ws:sel

See code: @adobe/aio-cli-plugin-console

aio discover

Discover plugins to install

USAGE
  $ aio discover

OPTIONS
  -f, --sort-field=date|name  [default: date] which column to sort, use the sort-order flag to specify sort direction
  -i, --install               interactive install mode

  -o, --sort-order=asc|desc   [default: desc] sort order for a column, use the sort-field flag to specify which column
                              to sort

DESCRIPTION
  To install a plugin, run 'aio plugins install NAME'

ALIASES
  $ aio plugins:discover

See code: src/commands/discover.js

aio help [COMMAND]

display help for aio

USAGE
  $ aio help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

aio info

Display dev environment version information

USAGE
  $ aio info

OPTIONS
  -j, --json  output raw json

See code: @adobe/aio-cli-plugin-info

aio jwt-auth:access-token

get the access token for the Adobe I/O Console

USAGE
  $ aio jwt-auth:access-token

OPTIONS
  -b, --bare                   print access token only
  -f, --force                  get a new access token
  -p, --passphrase=passphrase  the passphrase for the private-key
  --no-prompt                  do not prompt for passphrase

DESCRIPTION
  You must have a 'jwt-auth' key in your config, that has all your config data in .json format:
       aio config set jwt-auth --json --file path/to/your/config.json

EXAMPLE

  jwt_auth:
  {
     "client_id": "...",
     "client_secret": "..."
     "jwt_payload": {
       "iss": "...",
       "sub": "...",
       "...": true,
       "aud": "..."
     },
     "jwt_private_key": "/path/to/cert"
  }

See code: @adobe/aio-cli-plugin-jwt-auth

aio plugins

list installed plugins

USAGE
  $ aio plugins

OPTIONS
  --core  show core plugins

EXAMPLE
  $ aio plugins

See code: @oclif/plugin-plugins

aio plugins:install PLUGIN...

installs a plugin into the CLI

USAGE
  $ aio plugins:install PLUGIN...

ARGUMENTS
  PLUGIN  plugin to install

OPTIONS
  -f, --force    yarn install with force flag
  -h, --help     show CLI help
  -v, --verbose

DESCRIPTION
  Can be installed from npm or a git url.

  Installation of a user-installed plugin will override a core plugin.

  e.g. If you have a core plugin that has a 'hello' command, installing a user-installed plugin with a 'hello' command 
  will override the core plugin implementation. This is useful if a user needs to update core plugin functionality in 
  the CLI without the need to patch and update the whole CLI.

ALIASES
  $ aio plugins:add

EXAMPLES
  $ aio plugins:install myplugin 
  $ aio plugins:install https://github.com/someuser/someplugin
  $ aio plugins:install someuser/someplugin

See code: @oclif/plugin-plugins

aio plugins:link PLUGIN

links a plugin into the CLI for development

USAGE
  $ aio plugins:link PLUGIN

ARGUMENTS
  PATH  [default: .] path to plugin

OPTIONS
  -h, --help     show CLI help
  -v, --verbose

DESCRIPTION
  Installation of a linked plugin will override a user-installed or core plugin.

  e.g. If you have a user-installed or core plugin that has a 'hello' command, installing a linked plugin with a 'hello' 
  command will override the user-installed or core plugin implementation. This is useful for development work.

EXAMPLE
  $ aio plugins:link myplugin

See code: @oclif/plugin-plugins

aio plugins:uninstall PLUGIN...

removes a plugin from the CLI

USAGE
  $ aio plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

OPTIONS
  -h, --help     show CLI help
  -v, --verbose

ALIASES
  $ aio plugins:unlink
  $ aio plugins:remove

See code: @oclif/plugin-plugins

aio plugins:update

update installed plugins

USAGE
  $ aio plugins:update

OPTIONS
  -h, --help     show CLI help
  -v, --verbose

See code: @oclif/plugin-plugins

aio report

Report an issue with the CLI or submit a feature request

USAGE
  $ aio report

OPTIONS
  -b, --bug      report an issue
  -f, --feature  request a feature

See code: @adobe/aio-cli-plugin-info

aio rollback

Clears all installed plugins.

USAGE
  $ aio rollback

OPTIONS
  -c, --[no-]confirm  confirmation needed for clear (defaults to true)
  -i, --interactive   interactive clear mode
  -l, --list          list plugins that will be cleared

See code: src/commands/rollback.js

aio runtime

Execute runtime commands

USAGE
  $ aio runtime

OPTIONS
  -i, --insecure           bypass certificate check
  -u, --auth=auth          whisk auth
  -v, --verbose            Verbose output
  --apihost=apihost        whisk API host
  --apiversion=apiversion  whisk API version
  --cert=cert              client cert
  --debug=debug            Debug level output
  --help                   Show help
  --key=key                client key
  --version                Show version

ALIASES
  $ aio rt

See code: @adobe/aio-cli-plugin-runtime

aio runtime:action

Manage your actions

USAGE
  $ aio runtime:action

OPTIONS
  -i, --insecure           bypass certificate check
  -u, --auth=auth          whisk auth
  -v, --verbose            Verbose output
  --apihost=apihost        whisk API host
  --apiversion=apiversion  whisk API version
  --cert=cert              client cert
  --debug=debug            Debug level output
  --help                   Show help
  --key=key                client key
  --version                Show version

ALIASES
  $ aio rt:action

See code: @adobe/aio-cli-plugin-runtime

aio runtime:action:create ACTIONNAME [ACTIONPATH]

Creates an Action

USAGE
  $ aio runtime:action:create ACTIONNAME [ACTIONPATH]

OPTIONS
  -A, --annotation-file=annotation-file  FILE containing annotation values in JSON format
  -E, --env-file=env-file                FILE containing environment variables in JSON format
  -P, --param-file=param-file            FILE containing parameter values in JSON format
  -a, --annotation=annotation            annotation values in KEY VALUE format
  -e, --env=env                          environment values in KEY VALUE format
  -i, --insecure                         bypass certificate check
  -l, --logsize=logsize                  the maximum log size LIMIT in MB for the action (default 10)
  -m, --memory=memory                    the maximum memory LIMIT in MB for the action (default 256)
  -p, --param=param                      parameter values in KEY VALUE format

  -t, --timeout=timeout                  the timeout LIMIT in milliseconds after which the action is terminated (default
                                         60000)

  -u, --auth=auth                        whisk auth

  -v, --verbose                          Verbose output

  --apihost=apihost                      whisk API host

  --apiversion=apiversion                whisk API version

  --binary                               treat code artifact as binary

  --cert=cert                            client cert

  --debug=debug                          Debug level output

  --docker=docker                        [Restricted Access] use provided Docker image (a path on DockerHub) to run the
                                         action

  --help                                 Show help

  --json                                 output raw json

  --key=key                              client key

  --kind=kind                            the KIND of the action runtime (example: swift:default, nodejs:default)

  --main=main                            the name of the action entry point (function or fully-qualified method name
                                         when applicable)

  --sequence=sequence                    treat ACTION as comma separated sequence of actions to invoke

  --version                              Show version

  --web=true|yes|false|no|raw            treat ACTION as a web action or as a raw HTTP web action

ALIASES
  $ aio rt:action:create

See code: @adobe/aio-cli-plugin-runtime

aio runtime:action:delete ACTIONNAME

Deletes an Action

USAGE
  $ aio runtime:action:delete ACTIONNAME

OPTIONS
  -i, --insecure           bypass certificate check
  -u, --auth=auth          whisk auth
  -v, --verbose            Verbose output
  --apihost=apihost        whisk API host
  --apiversion=apiversion  whisk API version
  --cert=cert              client cert
  --debug=debug            Debug level output
  --help                   Show help
  --json                   output raw json
  --key=key                client key
  --version                Show version

ALIASES
  $ aio runtime:action:del
  $ aio rt:action:delete
  $ aio rt:action:del

See code: @adobe/aio-cli-plugin-runtime

aio runtime:action:get ACTIONNAME

Retrieves an Action

USAGE
  $ aio runtime:action:get ACTIONNAME

OPTIONS
  -i, --insecure           bypass certificate check
  -r, --url                get action url
  -u, --auth=auth          whisk auth
  -v, --verbose            Verbose output
  --apihost=apihost        whisk API host
  --apiversion=apiversion  whisk API version
  --cert=cert              client cert
  --debug=debug            Debug level output
  --help                   Show help
  --key=key                client key
  --save                   save action code to file corresponding with action name
  --save-as=save-as        file to save action code to
  --version                Show version

ALIASES
  $ aio rt:action:get

See code: @adobe/aio-cli-plugin-runtime

aio runtime:action:invoke ACTIONNAME

Invokes an Action

USAGE
  $ aio runtime:action:invoke ACTIONNAME

OPTIONS
  -P, --param-file=param-file  FILE containing parameter values in JSON format
  -b, --blocking               blocking invoke
  -i, --insecure               bypass certificate check
  -p, --param=param            parameter values in KEY VALUE format
  -r, --result                 blocking invoke; show only activation result (unless there is a failure)
  -u, --auth=auth              whisk auth
  -v, --verbose                Verbose output
  --apihost=apihost            whisk API host
  --apiversion=apiversion      whisk API version
  --cert=cert                  client cert
  --debug=debug                Debug level output
  --help                       Show help
  --key=key                    client key
  --version                    Show version

ALIASES
  $ aio rt:action:invoke

See code: @adobe/aio-cli-plugin-runtime

aio runtime:action:list [PACKAGENAME]

Lists all the Actions

USAGE
  $ aio runtime:action:list [PACKAGENAME]

OPTIONS
  -i, --insecure           bypass certificate check
  -l, --limit=limit        only return LIMIT number of actions from the collection (default 30)
  -n, --name               sort results by name
  -s, --skip=skip          exclude the first SKIP number of actions from the result
  -u, --auth=auth          whisk auth
  -v, --verbose            Verbose output
  --apihost=apihost        whisk API host
  --apiversion=apiversion  whisk API version
  --cert=cert              client cert
  --debug=debug            Debug level output
  --help                   Show help
  --json                   output raw json
  --key=key                client key
  --name-sort              sort results by name
  --version                Show version

ALIASES
  $ aio runtime:action:ls
  $ aio runtime:actions:list
  $ aio runtime:actions:ls
  $ aio rt:action:list
  $ aio rt:actions:list
  $ aio rt:action:ls
  $ aio rt:actions:ls

See code: @adobe/aio-cli-plugin-runtime

aio runtime:action:update ACTIONNAME [ACTIONPATH]

Updates an Action

USAGE
  $ aio runtime:action:update ACTIONNAME [ACTIONPATH]

OPTIONS
  -A, --annotation-file=annotation-file  FILE containing annotation values in JSON format
  -E, --env-file=env-file                FILE containing environment variables in JSON format
  -P, --param-file=param-file            FILE containing parameter values in JSON format
  -a, --annotation=annotation            annotation values in KEY VALUE format
  -e, --env=env                          environment values in KEY VALUE format
  -i, --insecure                         bypass certificate check
  -l, --logsize=logsize                  the maximum log size LIMIT in MB for the action (default 10)
  -m, --memory=memory                    the maximum memory LIMIT in MB for the action (default 256)
  -p, --param=param                      parameter values in KEY VALUE format

  -t, --timeout=timeout                  the timeout LIMIT in milliseconds after which the action is terminated (default
                                         60000)

  -u, --auth=auth                        whisk auth

  -v, --verbose                          Verbose output

  --apihost=apihost                      whisk API host

  --apiversion=apiversion                whisk API version

  --binary                               treat code artifact as binary

  --cert=cert                            client cert

  --debug=debug                          Debug level output

  --docker=docker                        [Restricted Access] use provided Docker image (a path on DockerHub) to run the
                                         action

  --help                                 Show help

  --json                                 output raw json

  --key=key                              client key

  --kind=kind                            the KIND of the action runtime (example: swift:default, nodejs:default)

  --main=main                            the name of the action entry point (function or fully-qualified method name
                                         when applicable)

  --sequence=sequence                    treat ACTION as comma separated sequence of actions to invoke

  --version                              Show version

  --web=true|yes|false|no|raw            treat ACTION as a web action or as a raw HTTP web action

ALIASES
  $ aio rt:action:update

See code: @adobe/aio-cli-plugin-runtime

aio runtime:activation

Manage your activations

USAGE
  $ aio runtime:activation

OPTIONS
  -i, --insecure           bypass certificate check
  -u, --auth=auth          whisk auth
  -v, --verbose            Verbose output
  --apihost=apihost        whisk API host
  --apiversion=apiversion  whisk API version
  --cert=cert              client cert
  --debug=debug            Debug level output
  --help                   Show help
  --key=key                client key
  --version                Show version

ALIASES
  $ aio rt:activation

See code: @adobe/aio-cli-plugin-runtime

aio runtime:activation:get [ACTIVATIONID]

Retrieves an Activation

USAGE
  $ aio runtime:activation:get [ACTIVATIONID]

OPTIONS
  -g, --logs               emit only the logs, stripped of time stamps and stream identifier
  -i, --insecure           bypass certificate check
  -l, --last               retrieves the most recent activation
  -u, --auth=auth          whisk auth
  -v, --verbose            Verbose output
  --apihost=apihost        whisk API host
  --apiversion=apiversion  whisk API version
  --cert=cert              client cert
  --debug=debug            Debug level output
  --help                   Show help
  --key=key                client key
  --version                Show version

ALIASES
  $ aio rt:activation:get

See code: @adobe/aio-cli-plugin-runtime

aio runtime:activation:list [ACTIVATIONID]

Lists all the Activations

Current Tags

  • 3.4.1                                ...           latest (9 days ago)

25 Versions

  • 3.4.1                                ...           9 days ago
  • 3.4.0                                ...           9 days ago
  • 3.3.0                                ...           a month ago
  • 3.2.0                                ...           2 months ago
  • 3.1.0                                ...           2 months ago
  • 3.0.0                                ...           4 months ago
  • 2.3.0                                ...           5 months ago
  • 2.2.3                                ...           6 months ago
  • 2.2.2                                ...           6 months ago
  • 2.2.1                                ...           6 months ago
  • 2.2.0                                ...           6 months ago
  • 2.1.1                                ...           7 months ago
  • 2.1.0                                ...           7 months ago
  • 2.0.1                                ...           10 months ago
  • 2.0.1-dev.0                                ...           10 months ago
  • 1.5.0                                ...           a year ago
  • 1.4.1                                ...           a year ago
  • 1.4.0                                ...           a year ago
  • 1.3.1                                ...           a year ago
  • 1.3.0                                ...           a year ago
  • 1.2.2                                ...           a year ago
  • 1.2.1                                ...           a year ago
  • 1.2.0                                ...           2 years ago
  • 1.1.0                                ...           2 years ago
  • 1.0.9                                ...           2 years ago
Downloads
Today 0
This Week 0
This Month 78
Last Day 0
Last Week 0
Last Month 51

Copyright 2014 - 2016 © taobao.org |