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.