### Example Installed Plugins List

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/types.md

Demonstrates the structure of the array returned by `Config.getPluginsList()`. This example shows how plugin metadata is represented, including core, user, and linked plugins.

```javascript
const plugins = this.config.getPluginsList()
// Result:
[
  {
    type: 'core',
    name: '@adobe/aio-cli-plugin-app',
    version: '14.2.1'
  },
  {
    type: 'user',
    name: '@my-org/custom-plugin',
    version: '1.0.0'
  },
  {
    type: 'core',
    name: '@adobe/aio-cli-plugin-config',
    version: '5.1.0'
  }
]
```

--------------------------------

### Plugin Discovery and Installation Flow

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/architecture.md

Illustrates the process initiated by the 'aio discover --install' command. It covers fetching from the npm registry, filtering, sorting, user selection via inquirer, and subsequent installation of selected plugins.

```bash
User: aio discover --install
  │
  ├─→ DiscoCommand.run()
  │
  ├─→ Fetch npm registry
  │   GET https://registry.npmjs.org/-/v1/search?text=aio-cli-plugin
  │
  ├─→ Filter packages (name starts with @adobe/aio-cli-plugin)
  │
  ├─→ Sort by date/name (sortValues helper)
  │
  ├─→ Show interactive checklist (inquirer)
  │   └─→ User selects plugins
  │
  ├─→ For each selected plugin:
  │   └─→ this.config.runCommand('plugins:install', [pluginName])
  │
  └─→ Return installed plugin names
```

--------------------------------

### Interactive Plugin Installation

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/api-reference/commands.md

Enters interactive mode to select and install plugins. The `--install` flag enables this feature, prompting the user to choose plugins.

```bash
aio discover --install
```

--------------------------------

### Install and Basic Usage of Adobe I/O CLI

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Shows how to install the CLI globally and demonstrates basic commands for checking version and help.

```sh
$ npm install -g @adobe/aio-cli
$ aio COMMAND
running command...
$ aio (--version|-v)
@adobe/aio-cli/11.1.2 darwin-arm64 node-v24.11.1
$ aio --help [COMMAND]
USAGE
  $ aio COMMAND
...
```

--------------------------------

### Discover Plugins to Install

Source: https://github.com/adobe/aio-cli/blob/master/README.md

This command helps discover installable plugins. It lists plugins with the prefix '@adobe/aio-cli-plugin'. To install a plugin, use 'aio plugins install NAME'.

```bash
aio discover [-i] [-f date|name] [-o asc|desc]
```

--------------------------------

### Display Autocomplete Installation Instructions

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Displays instructions for installing shell autocompletion. Supports zsh, bash, and powershell. The cache can be refreshed.

```bash
aio autocomplete [SHELL] [-r]
```

```bash
aio autocomplete
```

```bash
aio autocomplete bash
```

```bash
aio autocomplete zsh
```

```bash
aio autocomplete powershell
```

```bash
aio autocomplete --refresh-cache
```

--------------------------------

### Discover Plugins

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/INDEX.md

Lists available plugins, with options to sort by date or name, and to install them directly. Use this command to explore and manage your installed plugins.

```bash
aio discover [--sort-field date|name] [--sort-order asc|desc] [--install]
```

--------------------------------

### Install App Builder Template from Local Path

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Install an App Builder template from a local file path. Supports both relative and absolute paths.

```bash
aio templates install file:../relative/path/to/template/folder
```

```bash
aio templates install file:/absolute/path/to/template/folder
```

```bash
aio templates install ../relative/path/to/template/folder
```

```bash
aio templates install /absolute/path/to/template/folder
```

--------------------------------

### Install App Builder Template with Options

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Install an App Builder template with verbose output, skipping prompts, and passing additional template options as a base64-encoded JSON string.

```bash
aio templates i PATH [-v] [-y] [--install] [--process-install-config] [--template-options <value>]
```

--------------------------------

### Install App Builder Template with Options

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Installs an App Builder template with additional options, such as skipping prompts or processing install configurations. Template options can be provided as a base64-encoded JSON string.

```bash
aio templates install PATH [-v] [-y] [--install] [--process-install-config] [--template-options <value>]
```

--------------------------------

### Discover plugins in interactive install mode

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Enables interactive mode for discovering and installing plugins. The CLI will prompt for confirmation.

```bash
$ aio plugins discover -i
```

--------------------------------

### List Installed App Builder Templates

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Lists all installed App Builder templates. Use the `-j` flag for JSON output or `-s` to include required services.

```bash
aio templates info [-v] [-y | -j] [-s]
```

--------------------------------

### Check for Updates and Install

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/api-reference/commands.md

Checks for available plugin updates and installs them with user confirmation.

```bash
aio update
```

--------------------------------

### Example: User Plugin with Available Update

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/types.md

An example instance of ToUpdatePlugin representing a user-installed plugin that has a newer version available in the npm registry.

```javascript
{
  type: 'user',
  name: '@my-org/custom-plugin',
  currentVersion: '1.0.0',
  latestVersion: '1.1.0',
  coreVersion: null,
  needsUpdate: true,
  needsWarning: false
}
```

--------------------------------

### Example: Core Plugin Information

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/types.md

An example instance of ToUpdatePlugin for a core plugin, shown for informational purposes. Core plugins are not updated via the CLI.

```javascript
{
  type: 'core',
  name: '@adobe/aio-cli-plugin-app',
  currentVersion: '14.0.0',
  latestVersion: '14.2.1',
  coreVersion: '14.0.0',
  needsUpdate: true,
  needsWarning: false
}
```

--------------------------------

### Install App Builder Template from URL

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Install an App Builder template from a remote repository URL. Supports various URL formats including HTTPS, Git, and SSH.

```bash
aio templates install https://github.com/org/repo
```

```bash
aio templates install git+https://github.com/org/repo
```

```bash
aio templates install ssh://github.com/org/repo
```

```bash
aio templates install git+ssh://github.com/org/repo
```

--------------------------------

### Install a User Plugin

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/configuration.md

Use this command to install custom plugins developed by users or third parties. Ensure the plugin name is correctly specified.

```bash
aio plugins:install @my-org/custom-plugin
```

--------------------------------

### Install Adobe I/O CLI Plugin from npm

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Installs a plugin from the npm registry. This command uses npm for installation and can be used to add new functionality to the CLI.

```bash
aio plugins install myplugin
```

--------------------------------

### Install Adobe I/O CLI Plugin from GitHub URL

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Installs a plugin directly from a GitHub repository URL. This is useful for installing plugins not yet published to npm.

```bash
aio plugins install https://github.com/someuser/someplugin
```

--------------------------------

### Add a plugin from a GitHub slug

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Installs a plugin using its GitHub username and repository name (slug). This is a shorthand for installing from GitHub.

```bash
$ aio plugins add someuser/someplugin
```

--------------------------------

### Install Adobe I/O App Package

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Installs an Adobe I/O application package from a specified path. Supports options for verbose output, script execution, configuration validation, and running tests.

```bash
aio app install PATH [-v] [--version] [--config-validation] [--allow-scripts] [-o <value>] [--tests] [--no-allow-scripts] [--no-config-validation] [--no-tests]
```

--------------------------------

### Get Help

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/INDEX.md

Displays help information for the CLI or specific commands. This utilizes a custom help class for enhanced user guidance.

```bash
aio --help
aio -h
aio <command> --help
```

--------------------------------

### Discover and sort plugins by date (descending)

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Discovers plugins available for installation, sorted by date in descending order. This is the default behavior.

```bash
$ aio plugins discover
```

--------------------------------

### Add a plugin from npm registry

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Installs a plugin from the npm registry. Ensure the plugin name is correct.

```bash
$ aio plugins add myplugin
```

--------------------------------

### Add a plugin from a GitHub URL

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Installs a plugin directly from a GitHub repository URL. This is useful for plugins not yet published to npm.

```bash
$ aio plugins add https://github.com/someuser/someplugin
```

--------------------------------

### PrintTable Basic Usage Example

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/api-reference/table.md

Demonstrates how to use printTable with an array of data and basic column definitions, including fixed width and minimum width constraints.

```javascript
const { printTable } = require('@adobe/aio-cli/src/table')
const chalk = require('chalk')

// Example 1: Simple table
const plugins = [
  { name: '@adobe/plugin-a', version: '1.2.0' },
  { name: '@adobe/plugin-b', version: '2.0.1' }
]

printTable(plugins, {
  'Plugin Name': {
    width: 20,
    get: row => row.name
  },
  'Version': {
    minWidth: 10,
    get: row => row.version
  }
})
```

--------------------------------

### Example: User Plugin Overriding Core Plugin (Warning Case)

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/types.md

An example instance of ToUpdatePlugin where a user-installed plugin overrides a core plugin, and the user's version is older or equal to the core version, triggering a warning.

```javascript
{
  type: 'user',
  name: '@adobe/aio-cli-plugin-config',
  currentVersion: '5.0.0',
  latestVersion: '5.1.0',
  coreVersion: '5.1.0',
  needsUpdate: false,
  needsWarning: true  // User version is older than core version
}
```

--------------------------------

### Plugin Update Check and Installation Flow

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/architecture.md

Details the data flow for the 'aio update --interactive' command. It explains how installed plugins are checked for updates, versions are compared, and user-selected plugins are updated.

```bash
User: aio update --interactive
  │
  ├─→ UpdateCommand.run()
  │
  ├─→ GetPluginsList (oclif)
  │   └─→ Returns [InstalledPlugin, ...]
  │
  ├─→ For each plugin:
  │   ├─→ Fetch latest version from npm (getNpmLatestVersion)
  │   ├─→ Compare versions (semver.gt)
  │   ├─→ Check for overrides (plugin.type === 'user' && inCore)
  │   └─→ Construct ToUpdatePlugin
  │
  ├─→ Categorize plugins:
  │   ├─→ needsUpdateCore (info only)
  │   ├─→ needsUpdateUserNonCore (can update)
  │   ├─→ needsWarning (user override of old version)
  │   └─→ needsUpdateCoreButUserInstalled (rollback first)
  │
  ├─→ Display warnings and tables
  │
  ├─→ Interactive mode: Show checkbox
  │   └─→ User selects plugins to update
  │
  ├─→ For each selected plugin:
  │   ├─→ hideNPMWarnings() (if not --verbose)
  │   └─→ this.config.runCommand('plugins:install', [pluginName])
  │
  └─→ Return updated plugin names
```

--------------------------------

### Oclif Configuration Example

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/api-reference/AIOCommand.md

This JSON configuration object defines oclif settings for the Adobe I/O CLI, including command paths, plugins, and help class.

```json
{
  "oclif": {
    "topicSeparator": " ",
    "commands": "./src/commands",
    "bin": "aio",
    "helpClass": "./src/custom-help",
    "plugins": [
      "@oclif/plugin-help",
      "@oclif/plugin-plugins",
      "@oclif/plugin-autocomplete",
      "@oclif/plugin-not-found",
      "@oclif/plugin-warn-if-update-available",
      "@adobe/aio-cli-plugin-config",
      "@adobe/aio-cli-plugin-console",
      "@adobe/aio-cli-plugin-runtime",
      "@adobe/aio-cli-plugin-app",
      "@adobe/aio-cli-plugin-app-dev",
      "@adobe/aio-cli-plugin-app-storage",
      "@adobe/aio-cli-plugin-app-templates",
      "@adobe/aio-cli-plugin-auth",
      "@adobe/aio-cli-plugin-certificate",
      "@adobe/aio-cli-plugin-info",
      "@adobe/aio-cli-plugin-events",
      "@adobe/aio-cli-plugin-telemetry"
    ]
  }
}
```

--------------------------------

### Configure Log Forwarding Destination (Interactive)

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Use this command for an interactive setup of your log forwarding destination. It allows for flexible configuration through prompts.

```bash
aio rt namespace log-forwarding set [--cert] [--key] [--apiversion] [--apihost] [-u] [-i] [--debug <value>] [-v] [--version]
    [--help]
```

--------------------------------

### Check Plugin Compatibility

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/examples.md

List installed plugins and check for core plugin overrides to ensure compatibility. Use rollback commands if warnings appear or issues arise.

```bash
# List all installed plugins with versions
aio rollback --list

# Check for core plugin overrides
aio update --list

# If warnings appear, review and rollback if needed
aio rollback --interactive
```

--------------------------------

### List User Plugins Without Uninstalling

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/api-reference/commands.md

Uses the `--list` flag to display installed user plugins without performing any uninstallation.

```bash
aio rollback --list
```

--------------------------------

### Rollback CLI Command Usage

Source: https://github.com/adobe/aio-cli/blob/master/README.md

This snippet shows the usage and available flags for the `aio rollback` command, which clears installed plugins. Use the interactive flag for a guided process.

```bash
USAGE
  $ aio rollback [-i] [-l] [-c] [-v]

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

DESCRIPTION
  Clears all installed plugins.
```

--------------------------------

### Get Log Forwarding Errors CLI Usage

Source: https://github.com/adobe/aio-cli/blob/master/README.md

This snippet outlines the USAGE and FLAGS for retrieving log forwarding errors in Adobe I/O Runtime namespaces. Use this command to diagnose issues with your log forwarding setup.

```bash
USAGE
  $ aio rt ns log-forwarding errors [--cert] [--key] [--apiversion] [--apihost] [-u] [-i] [--debug <value>] [-v] [--version]
    [--help]

FLAGS
  -i, --insecure       bypass certificate check
  -u, --auth           [env: WHISK_AUTH] whisk auth
  -v, --verbose        Verbose output
      --apihost        [env: WHISK_APIHOST] whisk API host
      --apiversion     [env: WHISK_APIVERSION] whisk API version
      --cert           client cert
      --debug=<value>  Debug level output
      --help           Show help
      --key            client key
      --version        Show version

DESCRIPTION
  Get log forwarding errors

ALIASES
  $ aio runtime ns log-forwarding errors
  $ aio runtime ns lf errors
  $ aio runtime namespace lf errors
  $ aio rt namespace log-forwarding errors
  $ aio rt namespace lf errors
  $ aio rt ns log-forwarding errors
  $ aio rt ns lf errors
```

--------------------------------

### Read Local NPM Package Version

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/api-reference/helpers.md

Use this function to get the version of an npm package installed locally within the CLI's node_modules directory. It reads the package.json file directly and will throw errors if the file is not found or invalid.

```javascript
async getNpmLocalVersion(cliRoot, npmPackageName) → Promise<string>

Reads the version of an npm package installed in the CLI's node_modules directory.

Returns `Promise<string>` that resolves to the version string extracted from the package's package.json.

1. Constructs the path: `{cliRoot}/node_modules/{npmPackageName}/package.json`
2. Reads the file using `fs.readFileSync()` (blocking I/O)
3. Parses JSON and extracts the `version` field
4. Returns the version string

Throws an error if the file doesn't exist, is unreadable, or is invalid JSON.
```

```javascript
const { getNpmLocalVersion } = require('@adobe/aio-cli/src/helpers')

// Get installed version from CLI's node_modules
const installedVersion = await getNpmLocalVersion('/usr/local/lib/node_modules/@adobe/aio-cli', '@adobe/aio-cli-plugin-app')
console.log(`Installed version: ${installedVersion}`) // e.g., "14.0.0"
```

--------------------------------

### Initialize a New App Builder Project

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Use this command to create a new App Builder Project. You must provide a name for the project. Optional flags allow setting a description, title, and specifying the organization ID.

```bash
aio console project init -n <value> [--help] [-o <value>] [-t <value>] [-d <value>] [-j | -y]
```

--------------------------------

### Install Adobe I/O CLI Plugin from GitHub Slug

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Installs a plugin using its GitHub username and repository name (slug). This provides a shorthand for installing from GitHub.

```bash
aio plugins install someuser/someplugin
```

--------------------------------

### Display CLI Help

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/examples.md

Access help documentation for the CLI. Use `--help` or `-h` for general help or specific commands.

```bash
# Display main help
aio --help
aio -h

# Display help for specific command
aio discover --help
aio discover -h

# Display help for command with alias resolution
aio rt --help
# Shows 'runtime' subcommands (alias 'rt' → 'runtime')
```

--------------------------------

### Conditional AIO Plugin Installation Script

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/examples.md

Bash script to conditionally install AIO CLI plugins based on the NODE_ENV environment variable. Installs different sets of plugins for production and development environments.

```bash
#!/bin/bash
# Install plugins based on environment

if [ "$NODE_ENV" = "production" ]; then
  aio plugins:install @adobe/aio-cli-plugin-app
  aio plugins:install @adobe/aio-cli-plugin-config
else
  # For development, include additional plugins
  aio plugins:install @my-org/dev-tools
  aio plugins:install @my-org/debug-plugin
fi

aio update --list
```

--------------------------------

### Display Certificate Help

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Shows the general help information for the `aio certificate` command.

```bash
aio certificate
```

--------------------------------

### List Updates Without Installing

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/api-reference/commands.md

Lists plugins that have updates available without performing the installation.

```bash
aio update --list
```

--------------------------------

### aio app init Command Usage

Source: https://github.com/adobe/aio-cli/blob/master/README.md

This snippet shows the general usage and available flags for the `aio app init` command. Use this command to create a new Adobe I/O App, with options to specify installation path, templates, and configuration details.

```bash
USAGE
  $ aio app init [PATH] [--install] [-v] [--version] [--config-validation] [-y] [--login] [-e <value>... | -t
    <value>... | --repo <value>] [--standalone-app |  | ] [--template-options <value>] [-o <value> | -i <value> | ] [-p
    <value> |  | ] [-w <value> |  | ] [--confirm-new-workspace] [--use-jwt] [--github-pat <value> ] [--linter
    none|basic|adobe-recommended]

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

FLAGS
  -e, --extension=<value>...        Extension point(s) to implement
  -i, --import=<value>              Import an Adobe I/O Developer Console configuration file
  -o, --org=<value>                 Specify the Adobe Developer Console Org to init from (orgId, or orgCode)
  -p, --project=<value>             Specify the Adobe Developer Console Project to init from (projectId, or projectName)
  -t, --template=<value>...         Specify a link to a template that will be installed
  -v, --verbose                     Verbose output
  -w, --workspace=<value>           [default: Stage] Specify the Adobe Developer Console Workspace to init from,
                                    defaults to Stage
  -y, --yes                         Skip questions, and use all default values
      --[no-]config-validation      [default: true] Validate the app configuration file(s) before continuing.
      --[no-]confirm-new-workspace  Prompt to confirm before creating a new workspace
      --github-pat=<value>          github personal access token to use for downloading private quickstart repos
      --[no-]install                [default: true] Run npm installation after files are created
      --linter=<option>             [default: basic] Specify the linter to use for the project
                                    <options: none|basic|adobe-recommended>
      --[no-]login                  Login using your Adobe ID for interacting with Adobe I/O Developer Console
      --repo=<value>                Init from gh quick-start repo. Expected to be of the form <owner>/<repo>/<path>
      --standalone-app              Create a stand-alone application
      --template-options=<value>    Optional template options, as a base64-encoded json string
      --use-jwt                     if the config has both jwt and OAuth Server to Server Credentials (while migrating),
                                    prefer the JWT credentials
      --version                     Show version

DESCRIPTION
  Create a new Adobe I/O App

```

--------------------------------

### Get Persistent Config Value (aio config get)

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Retrieves a specific persistent configuration value. You can specify the key to get and choose between global or local configuration. Output can be formatted as JSON or YAML, and environment variables can also be accessed.

```bash
USAGE
  $ aio config get KEY [-l | -g] [-j | -y] [-e]

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

DESCRIPTION
  gets a persistent config value
```

--------------------------------

### Example Output with CustomHelp

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/api-reference/CustomHelp.md

Presents the expected help output when using the CustomHelp class for an aliased command like 'aio rt --help'. It shows the canonical command name and its subcommands.

```text
Adobe I/O Runtime

USAGE
  $ aio runtime COMMAND

TOPICS
  runtime:action      Manage actions
  runtime:activation  View activations
  runtime:build       Build runtime actions
  runtime:deploy      Deploy a project
  runtime:logs        Show runtime logs
  runtime:ns          Manage namespaces

COMMANDS
  runtime:action      Manage actions
  runtime:activation  View activations
  ...

```

--------------------------------

### Inspect Adobe I/O CLI Plugin

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Displays installation properties of a specified plugin. Use this to check details about an installed plugin.

```bash
aio plugins inspect PLUGIN...
```

--------------------------------

### Update Installed Plugins with AIO CLI

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Run this command to update all installed plugins for the AIO CLI to their latest versions. No arguments are required.

```bash
aio plugins update
```

--------------------------------

### Create Index with Multiple Keys

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Use this command to create an index based on multiple individual keys. This example creates an index on 'sku' and 'rating' for the 'reviews' collection.

```bash
aio app db index create reviews -k sku -k rating
```

--------------------------------

### Create Package Command Usage

Source: https://github.com/adobe/aio-cli/blob/master/README.md

This snippet shows the command usage for creating a package. It includes the required package name and various optional flags for configuration.

```bash
USAGE
  $ aio runtime package create PACKAGENAME [--cert <value>] [--key <value>] [--apiversion <value>] [--apihost <value>] [-u 
    <value>] [-i] [--debug <value>] [-v] [--version] [--help] [-p <value>...] [-P <value>] [--shared true|yes|false|no] 
    [-a <value>...] [-A <value>] [--json]

FLAGS
  -A, --annotation-file=<value>  FILE containing annotation values in JSON format
  -P, --param-file=<value>       parameter to be passed to the package for json file
  -a, --annotation=<value>...    annotation values in KEY VALUE format
  -i, --insecure                 bypass certificate check
  -p, --param=<value>...         parameters in key value pairs to be passed to the package
  -u, --auth=<value>             [env: WHISK_AUTH] whisk auth
  -v, --verbose                  Verbose output
      --apihost=<value>          [env: WHISK_APIHOST] whisk API host
      --apiversion=<value>       [env: WHISK_APIVERSION] whisk API version
      --cert=<value>             client cert
      --debug=<value>            Debug level output
      --help                     Show help
      --json                     output raw json
      --key=<value>              client key
      --shared=<option>          parameter to be passed to indicate whether package is shared or private
                                 <options: true|yes|false|no>
      --version                  Show version

DESCRIPTION
  Creates a Package

ALIASES
  $ aio runtime pkg create
  $ aio rt package create
  $ aio rt pkg create
```

--------------------------------

### Create New Adobe I/O App

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Initialize a new Adobe I/O application in a specified directory. Supports importing configurations and validation.

```bash
aio app create [PATH] [-v] [--version] [--config-validation] [-i <value>]
```

--------------------------------

### Display Help for aio CLI

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Shows the help documentation for the aio CLI and its commands. Use the -n flag to include nested commands.

```bash
aio help [COMMAND...]

```

--------------------------------

### Install App Builder Template from NPM Package

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Install an App Builder template directly from an NPM package. You can specify a package name, version, or tag.

```bash
aio templates install npm-package-name
```

```bash
aio templates install npm-package-name@tagOrVersion
```

```bash
aio templates install @scope/npm-package-name
```

```bash
aio templates install @scope/npm-package-name@tagOrVersion
```

--------------------------------

### Install Specific Plugin Update

Source: https://github.com/adobe/aio-cli/blob/master/RELEASING.md

Install the latest version of a specific plugin, such as the console plugin, after determining the necessary version update (major, minor, or patch).

```bash
npm install @adobe/aio-cli-plugin-console@latest --save
```

--------------------------------

### Adobe I/O CLI Runtime Get Property Command

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Get property details for Adobe I/O Runtime. Use the `--all` flag to retrieve all properties.

```bash
USAGE
  $ aio runtime prop get [--cert] [--key] [--apiversion] [--apihost] [-u] [-i] [--debug <value>] [-v] [--version] 
    [--help] [--namespace] [--all] [--apibuild] [--apibuildno] [--cliversion]

FLAGS
  -i, --insecure       bypass certificate check
  -u, --auth           [env: WHISK_AUTH] whisk auth
  -v, --verbose        Verbose output
      --all            all properties
      --apibuild       whisk API build version
      --apibuildno     whisk API build number
      --apihost        [env: WHISK_APIHOST] whisk API host
      --apiversion     [env: WHISK_APIVERSION] whisk API version
      --cert           client cert
      --cliversion     whisk CLI version
      --debug=<value>  Debug level output
      --help           Show help
      --key            client key
      --namespace      whisk namespace
      --version        Show version

DESCRIPTION
  get property

ALIASES
  $ aio runtime prop get
  $ aio rt property get
  $ aio rt prop get
```

--------------------------------

### List User Plugins

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/api-reference/commands.md

Displays a table of user-installed plugins and their versions. This is a read-only operation.

```text
plugin              version
─────────────────── ─────────
@my-org/plugin-a    1.2.0
@my-org/plugin-b    2.0.1
```

--------------------------------

### Get App Configuration with aio app config get

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Retrieve specific application configuration values using this command. It supports verbose output and configuration validation.

```bash
USAGE
  $ aio app config get [-v] [--version] [--config-validation]

FLAGS
  -v, --verbose                 Verbose output
      --[no-]config-validation  [default: true] Validate the app configuration file(s) before continuing.
      --version                 Show version

DESCRIPTION
  Get app config

ALIASES
  $ aio app config get
```

--------------------------------

### Discover and sort plugins by name (ascending)

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Discovers plugins and sorts them alphabetically by name. Use this to find plugins based on their names.

```bash
$ aio plugins discover -f name -o asc
```

--------------------------------

### List Adobe I/O Runtime Namespaces

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Lists all available namespaces for Adobe I/O Runtime. Use the `--insecure` flag to bypass certificate checks or `--auth` for authentication.

```bash
aio rt namespace list [--cert <value>] [--key <value>] [--apiversion <value>] [--apihost <value>] [-u <value>] [-i] [--debug <value>] [-v] [--version] [--help] [--json]
```

--------------------------------

### Get a specific state key using aio app state get

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Retrieves the value associated with a specific state key. Supports JSON output and region selection.

```bash
aio app state get KEY
```

```bash
aio app state get KEY --json
```

```bash
aio app state get KEY | wc -c
```

--------------------------------

### List Runtime Triggers, Actions, and Rules

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Use this command to list all triggers, actions, and rules registered within a specific namespace. It supports options for authentication, API host and version, and output formatting.

```bash
USAGE
  $ aio rt list [--cert <value>] [--key <value>] [--apiversion <value>] [--apihost <value>] [-u <value>] [-i]
    [--debug <value>] [-v] [--version] [--help] [--json] [--name-sort] [-n]

FLAGS
  -i, --insecure            bypass certificate check
  -n, --name                sort results by name
  -u, --auth=<value>        [env: WHISK_AUTH] whisk auth
  -v, --verbose             Verbose output
      --apihost=<value>     [env: WHISK_APIHOST] whisk API host
      --apiversion=<value>  [env: WHISK_APIVERSION] whisk API version
      --cert=<value>        client cert
      --debug=<value>       Debug level output
      --help                Show help
      --json                output raw json
      --key=<value>         client key
      --name-sort           sort results by name
      --version             Show version

DESCRIPTION
  Get triggers, actions, and rules in the registry for namespace

ALIASES
  $ aio rt get
  $ aio runtime list
  $ aio rt list
  $ aio runtime ls
  $ aio rt ls

```

--------------------------------

### Clear All Installed App Builder Templates

Source: https://github.com/adobe/aio-cli/blob/master/README.md

This command clears all installed App Builder templates. It can be run with confirmation flags or in interactive mode. Use the `--list` flag to see which templates will be uninstalled.

```bash
aio templates rollback
```

--------------------------------

### Instantiate and Parse Command

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/api-reference/commands.md

Use this pattern to define a command class, set its description, flags, and aliases, and parse arguments within the `run` method.

```javascript
class MyCommand extends Command {
  async run() {
    const { flags } = await this.parse(MyCommand)
    // ... execute command
  }
}

MyCommand.description = 'Command description'
MyCommand.flags = { /* flag definitions */ }
MyCommand.aliases = ['alias1', 'alias2']
```

--------------------------------

### List Available Plugins

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/api-reference/commands.md

Lists all available plugins from the npm registry, sorted by date in descending order. This is the default behavior when no flags are specified.

```bash
aio discover
```

--------------------------------

### InstalledPlugin Type Definition

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/INDEX.md

Represents a currently installed plugin. Used by all commands.

```typescript
{
  type: 'user' | 'core' | 'link',
  name: string,
  version: string
}
```

--------------------------------

### List Runtime Packages

Source: https://github.com/adobe/aio-cli/blob/master/README.md

This command lists available runtime packages. It supports various flags for authentication, API host, and debugging.

```bash
aio runtime pkg [--cert] [--key] [--apiversion] [--apihost] [-u] [-i] [--debug <value>] [-v] [--version] [--help]
```

--------------------------------

### List Runtime Packages

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Lists all available packages in a specified namespace. Supports filtering, sorting, and outputting raw JSON.

```bash
aio rt pkg ls [NAMESPACE] [--cert <value>] [--key <value>] [--apiversion <value>] [--apihost <value>] [-u <value>] [-i] [--debug <value>] [-v] [--version] [--help] [-l <value>] [-s <value>] [-c] [--json] [--name-sort] [-n]
```

--------------------------------

### Get Configuration Value

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Retrieves a specific persistent configuration value by its key.

```bash
$ aio config:get KEY
```

--------------------------------

### List Adobe I/O Runtime APIs

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Use this command to list route/APIs for Adobe I/O Runtime. It accepts optional base path, relative path, and HTTP verb as arguments. Various flags are available for customization, such as insecure connection, limit, skip, authentication, and output format.

```bash
USAGE
  $ aio rt api list [BASEPATH] [RELPATH] [APIVERB] [--cert <value>] [--key <value>] [--apiversion <value>]
    [--apihost <value>] [-u <value>] [-i] [--debug <value>] [-v] [--version] [--help] [-l <value>] [-s <value>] [--json]

ARGUMENTS
  [BASEPATH]  The base path of the api
  [RELPATH]   The path of the api relative to the base path
  [APIVERB]   (get|post|put|patch|delete|head|options) The http verb

FLAGS
  -i, --insecure            bypass certificate check
  -l, --limit=<value>       only return LIMIT number of triggers
  -s, --skip=<value>        exclude the first SKIP number of triggers from the result
  -u, --auth=<value>        [env: WHISK_AUTH] whisk auth
  -v, --verbose             Verbose output
      --apihost=<value>     [env: WHISK_APIHOST] whisk API host
      --apiversion=<value>  [env: WHISK_APIVERSION] whisk API version
      --cert=<value>        client cert
      --debug=<value>       Debug level output
      --help                Show help
      --json                output raw json
      --key=<value>         client key
      --version             Show version

DESCRIPTION
  list route/apis for Adobe I/O Runtime

ALIASES
  $ aio runtime api ls
  $ aio runtime route list
  $ aio runtime route ls
  $ aio rt api list
  $ aio rt api ls
  $ aio rt route list
  $ aio rt route ls
```

--------------------------------

### Plugin List Format

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/api-reference/commands.md

This is the expected format for the array returned by `this.config.getPluginsList()`, detailing installed plugins.

```javascript
[
  {
    type: 'core' | 'user' | 'link',
    name: '@adobe/aio-cli-plugin-app',
    version: '14.2.1'
  },
  // ...
]
```

--------------------------------

### Publish to npm

Source: https://github.com/adobe/aio-cli/blob/master/RELEASING.md

Publish the current version of the package to the npm registry, making it available for installation by users.

```bash
npm publish
```

--------------------------------

### Create Action Command Usage

Source: https://github.com/adobe/aio-cli/blob/master/README.md

This snippet shows the general usage and available flags for creating an action using the Adobe I/O CLI. It outlines parameters like ACTIONNAME and ACTIONPATH, along with numerous flags for configuration.

```bash
USAGE
  $ aio runtime action create ACTIONNAME [ACTIONPATH] [--cert <value>] [--key <value>] [--apiversion <value>] [--apihost
    <value>] [-u <value>] [-i] [--debug <value>] [-v] [--version] [--help] [-r] [-p <value>...] [--copy <value>] [-e
    <value>...] [--web-secure <value> --web true|yes|false|no|raw] [-P <value>] [-E <value>] [-t <value>] [-m <value>] [-l <value>] [-c <value>] [--kind <value>] [-a <value>...] [-A <value>] [--sequence <value>] [--docker <value>]
    [--main <value>] [--binary] [--json]

FLAGS
  -A, --annotation-file=<value>  FILE containing annotation values in JSON format
  -E, --env-file=<value>         FILE containing environment variables in JSON format
  -P, --param-file=<value>       FILE containing parameter values in JSON format
  -a, --annotation=<value>...    annotation values in KEY VALUE format
  -c, --concurrency=<value>      the maximum number of action invocations to send to the same container in parallel
                                 (default 200, min: 1, max: 500)
  -e, --env=<value>...           environment values in KEY VALUE format
  -i, --insecure                 bypass certificate check
  -l, --logsize=<value>          the maximum log size LIMIT in MB for the action (default 10, min: 0, max: 10)
  -m, --memory=<value>           the maximum memory LIMIT in MB for the action (default 256, min: 128, max: 4096)
  -p, --param=<value>...         parameter values in KEY VALUE format
  -r, --use-runtime-auth         use Runtime auth [default: false]
  -t, --timeout=<value>          the timeout LIMIT in milliseconds after which the action is terminated (default 60000,
                                 min: 100, max: 3600000)
  -u, --auth=<value>             [env: WHISK_AUTH] whisk auth
  -v, --verbose                  Verbose output
      --apihost=<value>          [env: WHISK_APIHOST] whisk API host
      --apiversion=<value>       [env: WHISK_APIVERSION] whisk API version
      --binary                   treat code artifact as binary
      --cert=<value>             client cert
      --copy=<value>             copy an existing action
      --debug=<value>            Debug level output
      --docker=<value>           [Restricted Access] use provided Docker image (a path on DockerHub) to run the action
      --help                     Show help
      --json                     output raw json
      --key=<value>              client key
      --kind=<value>             the KIND of the action runtime (example: swift:default, nodejs:default)
      --main=<value>             the name of the action entry point (function or fully-qualified method name when
                                 applicable)
      --sequence=<value>         treat ACTION as comma separated sequence of actions to invoke
      --version                  Show version
      --web=<option>             treat ACTION as a web action or as a raw HTTP web action
                                 <options: true|yes|false|no|raw>
      --web-secure=<value>       secure the web action (valid values are true, false, or any string)

DESCRIPTION
  Creates an Action

ALIASES
  $ aio rt action create
```

--------------------------------

### Get CLI Version

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/INDEX.md

Displays the current version of the Adobe I/O CLI. This is a built-in oclif command.

```bash
aio --version
aio -v
```

--------------------------------

### Update with Verbose Output and No Confirmation

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/api-reference/commands.md

Updates plugins, showing npm installation output and skipping the confirmation prompt.

```bash
aio update --no-confirm --verbose
```

--------------------------------

### Get System Information

Source: https://github.com/adobe/aio-cli/blob/master/_autodocs/INDEX.md

Displays information about the Adobe I/O CLI and the system environment. This is a built-in oclif command.

```bash
aio info
```

--------------------------------

### List Adobe I/O Runtime Routes

Source: https://github.com/adobe/aio-cli/blob/master/README.md

Lists all available routes and APIs for Adobe I/O Runtime. Supports filtering by base path, relative path, and HTTP verb. Use the --json flag for raw JSON output.

```bash
aio runtime route list [BASEPATH] [RELPATH] [APIVERB] [--cert <value>] [--key <value>] [--apiversion <value>]
  [--apihost <value>] [-u <value>] [-i] [--debug <value>] [-v] [--version] [--help] [-l <value>] [-s <value>] [--json]
```