March 8, 2018 | Written by: Steve Clay
Categorized: How-tos | What's New
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
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
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
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
-t option takes
buildpack for a Cloud Foundry deployment, or
container for a Kubernetes deployment.
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
IDT commands now return exit codes to indicate the success of execution.
There are a number of fixes, but a couple to draw your attention to:
debug command was not waiting for a debugger to attach to the debug port. This is returned to the behavior prior to
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.