What's New in IBM Cloud Developer Tools CLI Version 2.4.5

2 min read

Exciting new features and bug fixes in v2.4.5.

I’m pleased to announce the latest version of the IBM Cloud Developer Tools CLI. The following features are new, in addition to some bug fixes.

Cleaner application folder

The CLI no longer creates every kind of deployment file that could be used to deploy to IBM Cloud. As part of the create, edit, and enable commands, you can now select the type of deployment you plan to do for either a manual deployment or for toolchains and the necessary files for that deployment type will be created.

For example, the manifest.yml that’s used by Cloud Foundry will be created only if you select a Cloud Foundry deployment type. Through the edit command, you can add more deployment file types, should you need them later.

For example, the manifest.yml that’s used by Cloud Foundry will be created only if you select a Cloud Foundry deployment type. Through the edit command, you can add more deployment file types, should you need them later.

Toolchain API key generation

This release provides the API key that is used for toolchain deployment as output in the dialog. In prior releases, this key was created but not disclosed, which prevented reuse of the key. Now, as part of the toolchain creation, this key is shared with you. Take note of the key and then reuse it as needed for other access to IBM Cloud.

Cloud Foundry target now optional

With this release, the requirement to target your environment for Cloud Foundry is removed. Some options still require a Cloud Foundry org and space. The CLI now informs you when it is providing fewer options to you when Cloud Foundry is not targeted, but you no longer need to do this targeting to use most functions of the IBM Cloud Developer Tools CLI.

The following are some examples of items that still require Cloud Foundry org and space and, therefore, require you to run ibmcloud target –cf:

  • Manually deploying to Cloud Foundry
  • Creating a Cloud Foundry toolchain
  • Using a Cloud Foundry-based IBM Cloud service

Blank application type option is removed

The create command no longer presents the option of a Blank application type at the first prompt. There is no loss in capability, as the basic starter kit for each language that this option produces is still available by selecting the Backend Service / Web App application type.

Blank application type option is removed

Getting started with this release

Be the first to hear about news, product updates, and innovation from IBM Cloud