Package Manager Installation
Installers
- Debian 64 bit / 32 bit (deb)
- Redhat 64 bit / 32 bit (rpm)
- Mac OS X 64 bit (pkg)
- Windows 64 bit / 32 bit (zip)
Binaries
Change Log
Required TLS version is now 1.2
The cf CLI will now only negotiate TLS 1.2 connections. The cipher suites are restricted to those recommended by the Mozilla SSL Configuration Generator. For a full list of supported ciphers see the Cloud Foundry tlsconfig repo. story
Support for Log Cache
The cf CLI now streams logs from Log Cache instead of the soon to be deprecated Traffic Controller, Log Cache provides more stability to larger foundations, as well as reduced IAAS costs story
Fixed support window in CLI
The cf CLI will now properly warn users when using an incompatible CC API version (anything less than cf-deployment 7.0.0) story
Known Issues
-
For foundations with multiple log cache nodes: when streaming application staging logs, some log messages may be missing from the staging output. Those messages are subsequently available via
cf logs --recent. -
There is a known log cache issue on cf-deployment versions 7.0.0 through 9.5.0 (fixed in v10.0.0) where if a user pushes a new app very quickly after performing another logging action (less than a minute between) the API will fail to retrieve the logs for this new app, this typically occurs during the app staging process and will not prevent the app from successfully staging. Our recommended way to avoid this is to deploy at least cf-deployment 10.0.0
-
Experimental commands (those marked as v3-.. such as v3-zdt-push) do not stream logs from Log Cache. No logs will be shown when these commands are run against a foundation that does not have traffic controller enabled. This should not impact the results of the command
-
cf logs --recenterrors if there is > 4MB of logs returned (story). This is expected to be fixed in an upcoming release. Until then, our recommended mitigation is to use up to CF CLI v6.49.0 -
Log-cache-cf-auth-proxy does not support HS256. In CF CLI v6.50.0, we have moved over to using the log cache exclusively for log retrieval. If you have configured your UAA to use anything other than RS256, the log cache auth proxy does not know how to decode the UAA's tokens and will return 404. This is expected to be fixed in an upcoming log-cache release, so compatibility will be restored in a future cf-deployment version. Until then, our recommended mitigation is to use up to CF CLI v6.49.0
Contributors: Brendan Smith, Andrew Crump, Alexander Berezovsky, Steve Taylor, Eric Promislow, Jenna Goldstrich, Christopher Hendrix
Note: The minimum version of the CC API this CF CLI release is compatible with is CC API v2.128.0 (3.63.0). See our minimum supported version policy for more information.