Releases: apache/openwhisk-vscode
Debugger integration
New features include:
- updated to be compativle with latest NPM module & auth
- beta integration with OpenWhisk debugger (wskdb)
Debugger in action:
https://youtu.be/ANBJ5bilcbw
Installation instructions for side-loading extensions:
https://code.visualstudio.com/docs/extensions/install-extension#_install-a-packaged-extension-vsix
0.0.4
bug fixes and improvements:
- Generated file names are now unique when calling
wsk action initandwsk action get - Added support for Python actions
- Fixed silent failure when
wsk action initis invoked without a project folder - externalized new action templates (for
wsk action init) - this is for cleaner code, and better separation of template code from action VSCode extension code
0.0.3
0.0.2
0.0.1
Here is a pre-alpha version of the OpenWhisk extension for VS Code. Please feel free to give it a go. It should now be mostly functional for authoring OpenWhisk actions. I do not have functionality in there yet for managing packages, rules, or triggers yet.
To install the extension, just drag the .vsix file and drop it onto a running instance of VS Code. It will take a couple of seconds, and the extension will be installed automatically.
The intent is that is allows for very easy and very fast authoring and invocation of OpenWhisk without ever having to leave the editor. Before you can create actions, you will need to use wsk property set to set values for auth and namespace inside the VS Code editoring. You can get these values from either the web interface, or through the existing CLI. You can also set the apiHost property if you want to switch between staging and production environments.
This allows you to easily author and invoke OpenWhisk actions, enabling fast developer iteration cycles. When you invoke wsk action create or wsk action update, it uses the currently focused editor inside of VS Code, grabs the source, and pushes it up to OpenWhisk to create/update the action in the remote environment.
