In previous series of guides we configured Microsoft Visual Studio Code for common things like Arduino, WordPress development and debugging. In this guide we will discuss how to setup Visual Studio Code For IBM API and Bluemix on Mac. We will integrate CloudFoundry, Bluemix CLI and IBM Developer CLI. There are additional plugins for Microsoft Visual Studio Code which are useful for many Big Data related works, like an extension for OpenWhisk. We can actually install many of those softwares like Apache OpenWhisk on-premise. So the setup actually not fully IBM-only. IBM Data Science Experience Desktop is a separate matter and we will not discuss here.
Steps To Setup Visual Studio Code For IBM API & Bluemix on Mac
First you need to have Bluemix CLI and IBM Developer CLI plugin installed :
|
1 2 |
https://console.bluemix.net/docs/cli/reference/bluemix_cli/download_cli.html https://console.ng.bluemix.net/docs/cloudnative/dev_cli.html |
In case you have not installed both Bluemix CLI and IBM Developer CLI plugin, then you can install from iTerm2 in this way :
---
|
1 |
curl -sL https://ibm.biz/idt-installer | bash |
The above scripts will install dependencies including Bluemix CLI, Kubernetes, Helm, and Docker. You’ll get output like this :
|
1 2 3 4 5 6 |
[main] --==[ IBM Cloud Developer Tools - Installer, v1.0.1 ]==-- [install] Starting Full Installation... [install] Note: You may be prompted for your 'sudo' password during install. [install_deps] Checking for external dependency: git [install_deps] Checking for external dependency: docker ... |
Now after your command line setup is complete, start Visual Studio Code and install these four extensions :
IBM API Connect Tools
IBM Developer Tools
OpenWhisk
Output Colorizer
The Output Colorizer extension is a very useful tool for meaningful colorised output. After installing them simply reload Visual Studio Code.
In the above image you can see OpenWhisk extension in action. There is not much work on .zshrc file as the script does most of the works and essentially these extensions are not debuggers. The major advantage is some extra functions which otherwise not available via other extensions.
