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

Fix: bug with expired access token

Updated jwt-auth plugin with bug fix to the access token expiry check.

Fix: Adobe I/O Runtime API change (console:select-integration)

Added x-ims-org-id header to console:select-integration call

New features: support PEM files in config:set, added config:clear

• Added config:clear [key] to clear a specific key
• Added application/x-pem-file handling for config:set [key] --file (typically to set private keys)

New features: private-key passphrase support, .wskprops overwrite confirmation

For the console and jwt-auth commands, a --passphrase flag was added for you to specify a passphrase for your private-key if it is passphrase protected.

For the console:select-integration command, an interactive confirmation is presented to the user for overwriting the .wskprops file. An --overwrite flag can be set to bypass the prompt, to always overwrite the .wskprops file.

Initial release

Initial release of the console, config, and jwt-auth commands.