v0.7.0
This version is deprecated. Install the latest release.
Change logs
Support Cloud Foundry Enterprise Environment (CFEE)
IBM Cloud Foundry Enterprise Environment provides a tenant-specific Cloud Foundry environment for hosting a customer’s applications allowing compute isolation, administrative control and change management for the environment. This release adds the command lines to query the CFEE environments, show the detailed stats of a CFEE environment, the capability to select and target a CFEE environment so that the bundled cf cli can be used to manage the CFEE resources, and also the capability to alias a service instance into CFEE and bind to a CFEE application.
Support migration of Cloud Foundry service instance to resource group
This release adds the command to migrate a Cloud Foundry service instance to RC compatible service instance in a resource group if it is supported by the service
Add lock and unlock capability for service ID and API keys
Accidental deletion of service ID and API key may cause service outage. This release adds lock/unlock capability for service ID and API keys to help the user to prevent that.
Support global tagging of resources
This release incorporates a set of commands for managing the tags of Cloud resources
New commands
cfee environments: list the CFEE environments visible to the current usercfee environment: show the detailed stats of a CFEE environmentresource cf-service-instance-migrate: migrate a Cloud Foundry service instance to RC compatible service instance in a resource groupresource tags: list all tagsresource tag: show details of a tagresource tag-create: create a tagresource tag-delete: delete a tagresource tag-attach: add a tag to a resourceresource tag-detach: remove a tag from a resourceresource tag-update: switch user tag to restricted tag and vice versaiam service-id-lock: lock a service IDiam service-id-unlock: unlock a service IDiam api-key-lock: lock an API keyiam api-key-unlock: unlock an API keyiam service-api-key-lock: lock a service api keyiam service-api-key-unlock: unlock a service api key
Updated commands
target -r REGIONnow shows "not supported" instead of "not found" for regions that don't have cloud foundry deploymentresource service-instance,resource service-instance-updateandresource service-instance-deletenow allow using ID as argumenttarget --cfallows user to select and target either a public Cloud Foundry instance or CFEE environmenttarget --cf-apiallows user to target a public Cloud Foundry instance or CFEE environment by specifying the api endpoint of the Cloud Foundry instanceresource service-alias-createsupports creating a service alias in CFEE environmentresource service-binding-createallows binding a service instance to a CFEE application-v, --versionoption is removed fromiam access-group-policy-update,iam service-api-key-update,iam service-policy-updateandiam user-policy-updateiam service-ids,iam api-keysandiam service-api-keysadd a column to indicate whether the service ID or key is locked or notiam service-id-create,iam api-key-createandiam service-api-key-createadd--lockfunction to lock the service ID or api key when it is created.iam service-id-update,iam service-id-delete,iam api-key-update,iam api-key-delete,iam service-api-key-updateandiam service-api-key-deletewill fail if the service ID or api key is locked.iam access-group-policy-create,iam access-group-policy-update,iam user-policy-create,iam user-policy-update,iam service-policy-createandiam sevice-policy-updateadd validation of resource groupaccount user-deletechanges toaccount user-removeaccount user-inviteprovide options (-o,--org-role,-s,--space-role) to invite a user to org/space.
Defects fixing
- Some commands shows "not logged in" when user logs in dedicated environment with
--no-iamoption target --cffails when IAM token expiresiam oauth-tokensfails when logging in with--no-iamoption- Authorization policy created from
iam authorization-policy-createdoes not work when specifying the service instance in the policy
Other changes
- Upgrade to Golang 1.9.6
- Auto-completion is removed from system shell setting. The user needs to enable it by him/herself by sourcing the script in the user shell profile
- Installation path changes from
/usr/local/Bluemixto/usr/local/ibmcloud