I’m pleased to announce the 1.0.0 release of the IBM Cloud Command Line Interface.
In this release of the IBM Cloud CLI, we’ve introduced several important features and changes.
Additional JSON output support
To make it easier to write automation scripts, we’ve added the
–-output json global option, which you can use to get command output in JSON format. This option replaces the
–-output option for individual commands and extends it to most IBM Cloud CLI commands, including all classic infrastructure (
ibmcloud sl) commands. You can use this JSON output in combination with command-line JSON processing tools like
jq to automate tasks that you use to work in IBM Cloud.
Added quiet mode
--output option, we added the
--quiet global option for many commands. When
--quiet are used, some human-oriented helper text won’t be shown during command execution—for example:
Getting user details…. This feature reduces the number of extra messages in the command output to further simplify automated processing tasks.
Bundled IBM Cloud Developer Tools with the CLI
1.0.0, we’re now including the IBM Cloud Developer Tools (ibmcloud dev) with the IBM Cloud CLI. This means that, by default, you’ll be able to run commands to help build, test, deploy, and run apps in IBM Cloud, plus work with DevOps resources like pipelines and toolchains. In previous versions, the Developer Tools were available as a separate plug-in.
Removed bundled Cloud Foundry CLI
1.0.0, the Cloud Foundry CLI will no longer be bundled within the IBM Cloud CLI. You can still run Cloud Foundry CLI commands (
ibmcloud cf commands) from within IBM Cloud CLI, you just need install it separately using the
ibmcloud cf install command.
Added custom role support in access policy commands
IAM recently introduced custom roles to give you better access privilege control. In
1.0.0, you can list the custom roles using the
<a data-entity-substitution="" data-entity-type="" data-entity-uuid="" href="https://cloud.ibm.com/docs/cli?topic=cloud-cli-ibmcloud_commands_iam#ibmcloud_iam_roles" target="_blank">ibmcloud iam roles</a> command. These custom roles can be specified when creating access policies, including user policies, service policies, and access group policies.
Added resource group-level granularity for service-to-service authorization delegation
Previously, service-to-service authorization delegation abilities were limited to granting an authorization for a single instance of a service or all instances of the service in the account. In
1.0.0, you can specify all instances of a service within a resource group. We’ve added the
--target-resource-group-id options to accomplish this.
Getting started with this release