CF CLI v6.43.0 Released Today
The CF CLI team released cf CLI v6.43.0 today; please see release notes for full details.
Multi-Service Registration epic
CF now allows multiple service brokers to offer services with the same name and or to have the same catalogs. (However, brokers themselves must still be given a unique name.)
Note: Multi-service registration is only supported on CC API version 2.125.0 or greater.
Users can specify which broker to use with a new
-b flag, which is available on the following commands:
cf service- now display broker names
cf marketplacenow display broker names
Important Note: If you have two service instances with the same name, the commands above will now require the
-b flag to disambiguate which service instance and broker you want to operate on.
For more information: For more information regarding this feature and other services-related work in this release, reach out to cf-services-api@... or #sapi on Cloud Foundry Slack.
cf curlsupports a new
--failflag (primarily for scripting purposes) which returns exit code
22for server errors story
cf delete-orphaned-routessuch that it uses a different endpoint, reducing the chance of a race condition when two users are simultaneously deleting orphaned routes and associating routes with applications story
- we've improved the speed of cf services - it now hits a single endpoint instead of making individual API calls
Minimum Version Cleanup
Our minimum version policy changed in January 2019 to support CC API 2.100/3.35. This release removes code which support CC API below those versions. story
- Fixes issue with running
cf loginin verbose mode whereby passwords which contains regex were not completely redacted
- Fixes issue whilst running commands in verbose mode refresh tokens were not completely redacted
- Fixes a bug for users on 32-bit systems where the CLI would fail to unmarshall responses from the server because the response contained integer values that, when unmarshalled, would overflow 32-bit integers. For example, now users on 32-bit systems, can now set their memory usage larger than 2GB for
cf push. See the list of commands below which we've applied the fix for. story story
|CC Version||Resource||Field||Affected Commands|
|v2||App Instance Status||Disk|
|v2||App Instance Status||DiskQuota|
|v2||App Instance Status||Memory|
|v2||App Instance Status||Memory|
|v3||Process||Health Check Invocation Timeout|
Other Bug Fixes
- Updates help text for
- Now refresh tokens work properly whilst using
cf curlwith V3 CC API endpoints story
- Fixes performance degradation for
cf delete-servicerequires that you are targeting a space story
cf enable-service accessfor a service in an org will succeed if you have already enabled access for that service in that org story
Added anchor links to the plugin page story
updates autoscaler-cli story
updates log-cache-cli to
updates report-memory-usage story
adds log-stream plugin story
adds HTML5 Plugin v1.1.0 story
Thomas Viehman, Jennifer Spinney, Will Murphy, Magesh Kumar Murali, Alex Shan, Brendan Smith, Abby Chau, Aarti Kriplani, Alex Blease, Georgi Lozev, Henry Stanley, Laurel Gray, Niki Maslarski, Oleksii Fedorov, William Martin, Adam Eijdenberg (for the plugin page anchor links pull request), David Grizzanti (for the delete orphaned routes pr)
Thank you to all our Community contributors, we appreciate the pull requests!
Note: The minimum version of the CC API this CF CLI release is compatible with is CC API v2.100.0 (3.35). See our minimum supported version policy for more information.
CF CLI Team