September 1, 2017 | Written by: Steve Clay
Categorized: What's New
Share this post:
New features and fixes in version 1.0.0
of the IBM Cloud Developer Tools CLI which was formerly known as the Bluemix Developer CLI Plug-in.
Application Deployment to Kubernetes Environments
With this release, you can now deploy your application, packaged in a container to a Kubernetes environment such as the IBM Bluemix Container Service. The deployment is a simplified experience using Helm charts supplied through the
create and the Beta
enable command and the familiar
Enable Existing Applications for IBM Cloud Development (Beta)
You can now cloud-enable a Java, Node, Python or Swift server-side application you’ve already begun. The
enable command communicates with the IBM Cloud as the
create command does for a new project, creating required files cli-config.yml, Dockerfile, and Dockerfile-tools and creating merge files to allow inspection of any changes to existing files that may be required.
Simplified Access to the IBM Bluemix Console
console command is your shortcut from the command line bx dev experience to the IBM Bluemix Console. Invoking this command will open up your default system browser to your dashboard in the Bluemix console.
Coinciding with this new release of the Developer Tools CLI is the release of the IBM Developer Tools installer. This one command updates or installs the Developer Tools CLI and its prerequisites including the Bluemix CLI, the Docker engine, Helm, and the Kubernetes CLI. Instructions for using the installer are provided in the IBM Cloud Developer Tools documentation.
Improved Team Development Support
When you create a project using the Developer Tools CLI, the credentials for Bluemix services access are included in the project directories. However, when you commit this to a Git repository, those credentials will clearly be excluded. Thus a future clone of the Git project will be lacking the credentials.
The Developer Tools CLI now offers the
get-credentials command. For the above project that is cloned from a Git repository, this new command will download the credentials to the newly cloned local project.
Improved Project State Awareness
The Developer Tools CLI has now added more internal awareness of actions completed by the user. The primary example being what type of build of the project has been completed. This knowledge is then used to validate downstream actions such that the
debug commands, now require that a
build --debug has been completed before they can execute.
Docker Version Validation
The Docker version installed on the client is now validated to ensure compatibility with the Developer Tools CLI.
Validation of Bluemix Org and Space
The Bluemix CLI as of version 0.5.6 no longer forces the selection of an Org and Space. As many of the Developer Tools CLI functions do require the Org and Space, these settings are now validated for the functions that require them.
Windows Uses “root” User in Docker Containers
When executing commands on a Windows client, the
root user is always used in the Docker container, regardless of adding statements to the Dockerfile for using the current user.