What’s included in the IBM Cloud Developer Tools CLI version 1.2.0

Share this post:

New features and fixes in version 1.2.0 of the IBM Cloud Developer Tools CLI.

Expedite Your IDT Use with Compound Commands

New in this release we have added compound commands support.  With compound commands you can sequentially execute multiple IDT commands with one line of instruction.  The syntax for this new feature is:

idt command1/command2/... --flag1 --flag2 ...

Commands are executed sequentially from left to right.  For example, if I want to build my application, execute my tests against it, and then interactively debug it, I would use this syntax from my application folder:

idt build/test/debug --debug --trace

The flags for all of the commands are included at the end of the instruction.  The order of the flags does not matter, compound commands will apply each flag only to those commands for which it is relevant.  In this case --debug is only applicable to build and is ignored for the other commands.  --trace however, is applied to all the commands since they all support this flag.

The commands for use with compound commands are:

build, debug, deploy, get-credentials, run, stop, test, and view.

Receive Once-Daily Helpful Messages

With this release, we have added the facility to send timely messages to IDT users.  These messages will only appear once per day as you work with your application and will be used to notify you of important events relevant to your use of IDT.

Enable command now Recognizes Python Django

The enable command is expanded to recognize a Python Django project as it does Flask, already.  This allows a simple use of bx dev enable in your existing Django project folder, without the need to further indicate the language of the project.

Deployment Options for View

The view command now provides a command line option for the type of deployment to view, allowing for use of the command without prompting.  As with deploy, the -t option takes buildpack for a Cloud Foundry deployment, or container for a Kubernetes deployment.

The view command options also now include --ibm-cluster.  This option is the same as with deploy, allowing you to choose which Kubernetes cluster in the IBM Cloud specifically the application was deployed to, that you now wish to view.

Exit Codes Returned for Commands

The IDT commands now return exit codes to indicate the success of execution.

Defect Fixes

There are a number of fixes, but a couple to draw your attention to:

In version 1.1.4 the debug command was not waiting for a debugger to attach to the debug port.  This is returned to the behavior prior to 1.1.4.

Swift projects without special characters in the name (for example: -) were not including the compiled executable in the run image built by IDT.  This is now corrected.


Start developing your cloud native applications with IBM Cloud Developer Tools CLI today!  Create a new project or enable an existing one and enjoy a streamlined developer experience to get your applications on the IBM Cloud.

More How-tos stories

How to deliver great performance for global apps on IBM Cloud

A large telecommunications service provider in Europe wants to serve customers in Brazil from their Frankfurt, Germany location. One challenge with such large geographical distances is achieving consistently low latency in order to provide a good user experience. Another challenge is scaling the infrastructure to handle a large number of user requests during peak traffic conditions.

Continue reading

Securing your Python app with OpenID Connect (OIDC)

Some weeks back I introduced to a tutorial on how to analyse GitHub traffic. The tutorial combines serverless technology and Cloud Foundry to automatically retrieve statistics and store them in Db2. The data can then be accessed and analyzed using a Python Flask app. Today, I am going to show you how the web site is protected using OpenID Connect and IBM Cloud App ID.

Continue reading

Custom login page for App ID integration

When developing an application that integrates with App ID, the standard hosted login page has a few options to change the colours or logo. In some cases, this isn't enough and direct customisation is necessary. There exists a handy guide for a custom App ID login screen in mobile applications, however for web applications a little more effort is required.

Continue reading