Add core plugin @adobe/aio-cli-plugin-certificate, discover plugin

0aa2f0f (tag: 2.3.0) Incremented version to 2.3.0
7f61024 read package.json and gen health markdown table in readme (#101)
903858a Add @adobe/aio-cli-plugin-auth to health table
847f258 Add @adobe/aio-cli-plugin-auth as a core plugin
625a8b7 Update jest-fetch-mock to the latest version 🚀 (#96)
5b71d89 Update eslint-plugin-jest to the latest version 🚀 (#100)
10e4ce9 Update eslint-plugin-node to the latest version 🚀 (#99)
ea20b2a Merge pull request #98 from adobe/duynguyen-patch-1
88fad96 remove wskdebug install
9543248 Recommend to use nvm (#97)
a1d152b Add core plugin @adobe/aio-cli-plugin-certificate
c185c46 Update inquirer to the latest version 🚀 (#94)
9bcbb75 chore: update health matrix to add aio-cli-plugin-ims
a6cc1c1 Update jest-junit to the latest version 🚀 (#93)
1d8f8dc Update eslint-plugin-jest to the latest version 🚀 (#92)
4a2a66e Discover available plugins, and install them (#87)
4c6d1a1 Greenkeeper/eslint plugin jest 23.1.0 (#91)
e9f91b5 Update readme toc (#89)
0b68a1a (purplecabbage/master) Update readme with getting started guidance (#82)
63acafa Update eslint-plugin-jest to the latest version 🚀 (#81)
d8afb85 provide a relaxed tidelift config (#84)
2bfe6dc (tag: 2.2.3) 2.2.3
ac756ee fix: pin chalk@^2.4.2 in the cli -- npm tends to install chalk@latest which is v3.0.0, which is not specified anywhere in the dependency tree

2.2.3...2.3.0

fix: pin chalk@^2.4.2 in the cli (npm resolver issue)

• fix: pin chalk@^2.4.2 in the cli -- npm tends to install chalk@latest which is v3.0.0, which is not specified anywhere in the dependency tree ac756ee

2.2.2...2.2.3

Fix exception when running `aio plugins`

• fix: include package-lock.json in npm published tarball (#83) 363770a
• fix: disable Github Actions workflows (#80) 87c240b
• Update eslint-plugin-jest to the latest version 🚀 (#78) 5fa3bf1
• chore: add @adobe/aio-cli-plugin-app to health.xlsx 0bfe958
• fix: add @adobe/aio-cli-plugin-app to the health table 9e25523
• fix: re-add health table so it doesn't get clobbered by oclif-dev readme generation 1e41412

2.2.1...2.2.2

2.1.1

• updated dependent auto-install plugin @adobe/aio-cli-plugin-config@2.0.2

2.1.0

• Adobe Runtime plugin is now a core plugin
• updated dependencies of internal libs after numerous renames

1. Config Plugin
2. Jwt-Auth Plugin
3. Console Plugin
4. Runtime Plugin

2.0.1

INSTALLATION

In your terminal, type:
npm install @adobe/aio-cli

WHAT'S NEW

• local configuration file support ($CWD/.aio file)

# This a HJSON/JSON file named ".aio"
# This file is read from your current working directory (a.k.a $CWD)

$ cat .aio
{
   foo: bar
   mykey: myvalue
}

# now when your command is run, your config will have
console.log(config['foo']) // will print 'bar'
console.log(config['mykey']) // will print 'myvalue'

• environmental variable file support ($CWD/.env file)

# This a properties file named ".env", the keys and values will be added to `process.env`
# This file is read from your current working directory (a.k.a $CWD)

$ cat .env
foo=bar
mykey=myvalue

# now when your command is run, process.env will have
console.log(process.env['foo']) // will print 'bar'
console.log(process.env['mykey']) // will print 'myvalue'

• AIO_ prefixed environmental variable support: these variables will be added to your config at runtime

$ cat .env
AIO_mykey_mysubkey=myvalue
# for keys with underscores, use double underscores
AIO_akey_sub__key=avalue

# now when your command is run, your config will have
console.log(config['mykey.mysubkey']) // will print 'myvalue'
console.log(config['akey.sub_key']) // will print 'avalue'

# you can also prefix your command on unix-y systems with the key
AIO_mykey_mysubkey=myvalue aio console:list-integrations

• HJSON "human json" format support for configuration files:

  • object names don't have to be quoted
  • comments are allowed (block, single line etc)
  • multi-line strings are allowed
  • omit commas at the end of lines
  • trailing commas are allowed at the end of lists

• If you want to specify the location of the global configuration file, you can do so via environment variables (in order of precedence):

  • AIO_CONFIG_FILE
    if you set AIO_CONFIG_FILE=/my/global/folder/config.json to a file location, the CLI will load /my/global/folder/config.json as the global configuration
  • XDG_CONFIG_HOME
    if you set XDG_CONFIG_HOME=/my/global/folder to a a folder location, the cli will load the aio file from that folder, e.g. /my/global/folder/aio, as the global configuration
  • $HOME/.config/aio
    This is the default file location for your global configuration. $HOME is the current user's home folder

• The configuration is merged from the .env, local, and global configuration file locations. The precedence of the configuration values are:

  • .env file
  • local configuration file (.aio)
  • global configuration file

BREAKING CHANGES AND NEW FEATURES

1. Config Plugin
2. Jwt-Auth Plugin
3. Console Plugin

2.0.1-dev.0

pre-release. See official 2.0.1 release for Release Notes.

Updated console plugin to 1.4.0, new `aio console` behavior

aio-cli-plugin-console:

• Removed deprecated oclif-index-base-command module
• aio console with no sub-command is equivalent to aio console:list-integrations

New feature: support for "no colon separator" between sub-commands

Thanks to a successful surgery by Dr. @purplecabbage we have "no colon" support in this release.

So previously you would have to do this:
aio console:list-integration
Now you can do this as well:
aio console list-integration

other changes:

• removed TypeScript support
• changed the test-runner from Mocha to Jest

New feature: added `console:reset-integration` command

• Added console:reset-integration (console:reset) feature

This will reset the wsk auth code for an integration. Note: that if a previous command was already run, the credentials are cached for a max of 5 mins, then the auth code is revoked.

aio console:reset-integration INTEGRATION_ID