In this release of the IBM Cloud CLI, we’ve introduced several important features and changes.

Support for IBM Cloud Load Balancer

We’ve added the following commands under sl loadbal namespace to support the IBM Cloud Load Balancer service, which is a replacement of the former local load balancer service:

• list: List active load balancers
• order: Order a load balancer
• order-options: List options for order a load balancer
• protocol-add: Add a load balancer protocol
• protocol-delete: Delete a protocol
• cancel: Cancel an existing load balancer
• detail: Get load balancer details
• health-edit: Edit load balancer health check
• l7member-add: Add a L7 pool member
• l7member-delete: Remove a load balancer member
• l7policies: List L7 policies
• l7policy-add: Add an L7 policy
• l7policy-delete: Delete an L7 policy
• l7pool-add: Add an L7 pool
• l7pool-delete: Delete an L7 pool
• l7pool-detail: Show L7 pool details
• l7pool-edit: Edit an L7 pool
• l7rule-add: Add an L7 rule
• l7rule-delete: Delete an L7 rule
• l7rules: List l7 rules

Output CSV for billing commands

To facilitate billing reporting, we added --output csv support for the following billing commands:

• billing account-usage
• billing resource-instances-usage

Validation of service instance ID in policy commands

We introduced validation of service instance ID input in policy commands under iam namespace. The changes are shown below:

• access-group-policy-create, access-group-policy-update, user-policy-create, user-policy-update, service-policy-create, service-policy-update:
  • Check whether or not --service-instance input is valid.
• authorization-policy-create:
  • Check whether or not --target-service-instance-id input is valid.
  • If --source-service-account is not specified, then check whether or not --source-service-instance-id input is valid.

Additional deployment capabilities with the dev command

Manually deploy to Knative

With the latest dev commands, you can now deploy to Knative not only through a toolchain, but by using the deploy command. To use this feature, you must first create or enable an app. You also must have a Kubernetes cluster that includes Knative. You can find instructions for this configuration here. After those prerequisites are met, you can deploy to Knative by typing the following command from the app folder: 

ibmcloud dev deploy -t knative

The CLI will prompt you through the deployment.

Deploy to Red Hat OpenShift containers

Both toolchain and manual deployment to Red Hat OpenShift containers are now available. For deployment using a toolchain, the toolchain options that are now presented to you by create and edit include an additional option for RedHat OpenShift. You must have an OpenShift cluster available for the toolchain to succeed.

For manual deployment, the syntax is the same as for deploying to any other Helm-based Kubernetes cluster. To use this feature, you must first create or enable an app. You also must have an OpenShift cluster. After those prerequisites are met, you can deploy the app by typing the following command from the app folder:

ibmcloud dev deploy -t container

The CLI will prompt you through the deployment.

Other notable changes

• cfee namespace is deprecated.
• Upgrade to Go language 1.14.7 to resolve some security vulnerabilities. Customers are encouraged to upgrade to this release.

Getting started with this release

• Follow these instructions for a new installation, which includes the IBM Cloud CLI and other tools.
• To update an existing IBM Cloud CLI installation, run ibmcloud update.
• View the release notes: For a complete list of changes and defect fixes in this release, check out the release notes.
• Develop an app: Follow this tutorial to create or enable your first app.
• Feedback: Help us improve the IBM Cloud CLI by chatting with the developer team! Just sign up for IBM Cloud Technology Slack and join the #developer-tools channel. For questions about this blog, reach out to the author directly.