v0.15.0

This version is deprecated. Install the latest release.

Change logs

Log in with service ID

A service ID identifies a service or application similar to how a user ID identifies a user. You can assign specific access policies to the service ID that restrict permissions for access IBM Cloud resources. Since service IDs are not tied to a specific user, if a user happens to leave an organization and is deleted from the account, the service ID remains ensuring that your application or service stays up and running.

Starting from this release, logging in with a service ID api key is supported besides a normal user ID. Use the following steps to use this feature

• Create a service ID
• Create an API key of the service ID
• Log in with command ibmcloud login --apikey KEY where KEY is the api key string you created for the service ID.

Service Endpoint Support

If your account is VRF(Virtual Routing and Forwarding) enabled, you can specify service endpoint options when managing service instances.

• In resource service-instance-create and resource service-instance-update, you can enable public, private, or public-and-private endpoints for the service instance. Note that the available endpoint options are defined by the service in global catalog.
• In resource service-key-create and resource service-binding-create, you can select an endpoint type from the ones that were enabled when the service instance was created.

New commands

• account audit-logs: List Softlayer account audit logs

Updated Commands

• login: adds prompt to set proper IAM policy if logging in with service ID fails because of being not authorized to get account information.
• target: adds --output flag to generate JSON output
• account show:
  • adds account type, name and owner in output
  • show - instead of error messages when there is error in querying account VRF status
• resource service-instances: adds --type flag to filter instances by type.
• resource service-instance: shows the endpoint types if it is specified.
• resource service-instance-create:
  • adds validation to check wether the service is provisionable from command line
  • adds check to ensure all required parameters are specified
    • if required parameters are missing, default value (if exists) will be applied
  • adds --service-endpoints flag to specify the service endpoint types
• resource service-instance-update:
  • adds --service-endpoints flag to specify the service endpoint types
  • searches the service instance in all resource group is no resource group is targeted
• resource service-key-create:
  • adds --service-endpoint flag to specify the service endpoint type
  • removes options for system defined roles
• resource service-binding-create:
  • adds --service-endpoint flag to specify the service endpoint type
  • removes options for system defined roles
• iam: adds support to use * to specify all resource groups in IAM policy commands
• sl ticket: adds --priority flag

Defect Fixing

• resource cf-migrate-service: fail to migrate Cloud Foundry services when its service plan name is different from the name in resource catalog in letter case
• resource groups: default property is missing in the JSON output
• resource service-key-create, resource service-binding-create: remove support of system defined roles. Those two commands should only support service specific roles. Run ibmcloud iam roles --service SERVICE_NAME to get specific roles of each service.
• sl hardware list: nil pointer exception when some information is not available
• some command flags are not translated

Other changes

• sl commands: adds auto-refresh when the token expires