Releases: cloudfoundry/cli
v8.0.0
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
Docker
docker pull cloudfoundry/cli:8.0.0
Change Log
Release Notes
Services commands upgraded to call the v3 API
In v8 the cf CLI has been switched to using v3 CAPI to make service relates requests, most commands now have a new flag called --wait since v3 services code create async jobs, if you want to still synchronously wait you can use the new flag to wait for the operation to complete.
cf services
New flag --no-apps (Do not retrieve bound apps information)
New flag - --wait
cf marketplace
New Flag --show-unavailable (Show plans that are not available for use)
cf service
New Flag --params (Retrieve and display the given service instances's parameters. All other output is suppressed.)
Update - displays information about guid, type and broker tags
Update - service field is renamed to offering
Update - service broker
field is renamed to broker
Update - dashboard field is renamed to dashboard url
Update - The ordering and wording of each block of information have changed slightly
cf create-service
New flag --wait (Wait for the operation to complete)
param SERVICE
is now called SERVICE_OFFERING
cf update-service
New flag --wait (Wait for the operation to complete)
Removed Flag --upgrade
cf upgrade-service
Removed Flag --force
cf delete-service
New flag --wait (Wait for the operation to complete)
cf bind-service
New Flag --wait (Wait for the operation to complete)
cf unbind-service
New Flag --wait (Wait for the operation to complete)
cf service-key
Update - Displays information about last operation and message as new columns.
cf create-service-key
New Flag --wait (Wait for the operation to complete); operation is asynchronous by default
cf delete-service-key
New Flag --wait (Wait for the operation to complete); operation is asynchronous by default
cf bind-route-service
New Flag --wait (Wait for the operation to complete); bind-route-service is asynchronous by default
cf unbind-route-service
New Flag --wait (Wait for the operation to complete)
Operation is asynchronous by default
cf routes
Update added service instance column to output
Golang Bump to 1.16 from 1.13
This golang bump introduces a requirement for a SAN (Subject Alternative Name) in certificates used CF. Read more about this change here
Manifest Diffs
When applying a manifest in v8, for example during a push, you will not see manifest output provided through the new v3 space manifest diff endpoint. There are several known issues in this endpoint depending on what version of CAPI you use, see CAPI release notes for more info.
Support HTTP/2 When Mapping Routes
cf map-route
Users can specify destination protocol when mapping routes using the --destination-protocol
flag #2192
See the official Cloud Foundry documentation for more information on HTTP/2 routing for applications.
View Route Details
cf route
New command for viewing details about a route and its destinations #2205
Other
Removed v6/v2 dead code in several directory paths (command/v6 as an example)
Special thanks to our many contributors to the v8 release, including but not limited to:
Sarah Weinstein, Marc Paquette, Ryker Reed, Juan Diego Gonzalez, Dominic Roberts, Hema Ranganathan, Alexander Berezovsky, Jenna Goldstrich, Reid Mitchell, Mona Mohebbi, Teal Stannard, Seth Boyles, George Blue, Felisia Martini, Weyman Fung, Marcela Campo, Winna Bridgewater, Piyali Banerjee, Carson Long, and Klaas van Schelven
v7.3.0
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
Golang Bump to 1.16 from 1.13
This golang bump introduces a requirement for a SAN (Subject Alternative Name) in certificates used CF. Read more about this change here
Changes
Change CLI strategy for streaming logs from log cache, delaying when messages aren't found by 250 MS to decrease excessive load on log cache -> #2177
Add --wait to run-task -> 8671a5b
Two spaces indent for json ->e951a00
Add support for quotas to be given in TBs -> b9e606e
Support TLS 1.3 -> #2191
Bug Fixes
Stack being overriden on cf push #2148
V7 services do not poll empty jobs -> 7fb7b89
Cancel deployment v7 push on failure -> #2170
dfe195d -> Special characters are not HTML encoded
Contributors
Reid Mitchell, Jenna Goldstrich, Alexander Berezovsky, Dominic Roberts, Juan Diego Gonzalez, Hema Ranganathan, Teal Stannard, Seth Boyles, Zach Robinson, Felisia Martini, George Blue, Sarah Weinstein, Colin Simmons and Ryker Reed
v7.2.0
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
Bugs
- Logout is idempotent story
- CF Scale works on stopped apps issue
- CLI doesn't fail listing large numbers of apps issue
- CLI doesn't fail on login in certain Windows environments issue
cf network-policies
can query in spaces with many apps issue- CLI fails informatively when Cloud Controller fails without an error issue
Features
- Add
cf revisions
story- this initial iteration of the rollback command is experimental. Additional changes should be expected in the near-term v7 releases.
- Improved
cf revisions
help text story - Improve
cf revisions
: annotate which revision is deployed story - Improve
cf revisions
: tell user if app is stopped story - Improvements to
cf rollback
Contributors
Nick Webb, Lisa Burns, James Palmer, Alex Berezovsky, Josh Collins, Jenna Goldstrich, Steve Taylor,
Sebatian Vidrio, Sarah Weinstein, Harsha Nandiwada, George Blue, Derik Evangelista, Teal Stannard
Note: The minimum version of the CC API this CF CLI release is compatible with is CC API v3.85.0.
See our minimum supported version policy for more information.
v6.53.0
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
Corresponding BOSH Release
Change Log
Bugs
- Fix regression released in v6.52.0 whereby
cf logout
would exit non-zero when run without an api being targeted - issue
Contributors
Lisa Burns, James Palmer, Nick Webb, Jenna Goldstrich, Alexander Berezovsky, Steve Taylor, Josh Collins
Note: The minimum version of the CC API this CF CLI release is compatible with is CC API v2.128.0.
See our minimum supported version policy for more information.
v7.1.0
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
Compatibility
Tested against CC API Release Candidate capi-1.99.0-rc.33.
Change Log
FEATURE
cf rollback
- user can rollback to a previous app revision story- this initial iteration of the rollback command is experimental. Additional changes should be expected in the near-term v7 releases.
IMPORTANT NOTE: rollbacks are executed using the zero downtimerolling
deployment strategy which means both versions of the app will be running in parallel during the rollback.
- this initial iteration of the rollback command is experimental. Additional changes should be expected in the near-term v7 releases.
Enhancements
deployable
boolean added tocf revisions
outputrevisions
now shows an extra warning when revisions for that app are disabled - storyrevisions
now has several different header titles on the output table, and now revisions are shown in descending order - story- Add buildpack details in tabular format to
cf app
output issue # 1971- Add buildpack details in tabular format to
cf push
output
- Add buildpack details in tabular format to
- Improve misleading error message when un-sharing service-instances issue #1936
- Add logic to revoke auth and refresh tokens on CLI logout when revocable flag for UAA is present
- Improved
cf push
error messaging on manifest type errors issue #1983
Known Issues
- a regression of
cf logout
when no API is targeted, causing it to exit with a non-zero exit code was introduced in cf CLI v7.0.2. This causescf logout
to not be idempotent. The fix can be tracked here.
Contributors:
CLI Team:
James Palmer, Nick Webb, Jenna Goldstrich, Alexander Berezovsky, Steve Taylor, Josh Collins, Lisa Burns, Sebastian Vidrio
VAT Team:
Teal Stannard, Merric de Launey, Sarah Weinstein, Mona Mohebbi, Renee Chu, Chris Selzo, Reid Mitchell, Harsha Nandiwada, Greg Cobb
SAPI Team:
Aditya Tripathi, Brian Butz, Derik Evangelista, Emina Cosic, Marcela Campo, Urse Searle, Winna Bridgewater, Felisia Martini, George Blue
Other OSS Contributors:
Olivier Lechevalier, Xinhu Liu, Oliver Rand
Note: The minimum version of the CC API this CF CLI release is compatible with is CC API v3.85.0. See our minimum supported version policy for more information.
v6.52.0
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
FEATURE
- Legacy plugins use Log Cache - story
NOTE: We bumped the config as part of the implementation. CLI users that had targeted and logged into their foundations prior to updating to this CLI version may be required to to re-login & target in order to initialize the updated config.
Enhancements
- Invalidate UAA auth and refresh tokens on logout
- Add logic to revoke tokens on CLI logout when revocable flag for UAA is present
- Improved redaction in UAA verbose logging
- If UAA provides standard prompts (Email, Password) then the CLI can translate
them into the user's locale; else will display the prompt provided by UAA platform
operator.- Thanks @frodenas for PR'ing the sample translation for Spanish
- Provide localized prompt if sso is misconfigured - story
Bugs
- Lowercase hostname in
map-route
- story - Correct an issue with the update-service command where command was removing the tags on service when no tags were provided.
Contributors:
James Palmer, Nick Webb, Jenna Goldstrich, Alexander Berezovsky, Steve Taylor, Josh Collins, Andrew Crump, Olivier Lechevalier, Xinhu Liu, Lisa Burns, Sebastian Vidrio
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.
v7.0.2
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
Bug Fixes
- Double encode name parameters in requests to CAPI #1938
- Fixes known issue from previous release
v7.0.1
-- regression in the login behavior where failures occur on certain cf-deployments which use alternative login paths other than UAA #1964 - Allow empty space characters in app names #1966
Deletions
Remove leftover, experimental v3-zdt- commands
These commands were meant to be removed, since they have been replaced by the following commands
v3-zdt-restart
->restart --strategy rolling
v3-cancel-zdt-push
->cancel-deployment
Contributors: James Palmer, Nick Webb, Jenna Goldstrich, Alexander Berezovsky, Steve Taylor, Josh Collins, George Blue, Belinda Liu, Reid Mitchell, Sarah Weinstein
Note: The minimum version of the CC API this CF CLI release is compatible with is CC API v3.85.0. See our minimum supported version policy for more information.
v7.0.1
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
- Fix package management versioning issue
Known Issues
- Windows binary zip files do not include a symbolic link from
cf7 -> cf
due to lack of.zip
support for symbolic links on Windows. - There's been a regression in the login behavior where failures occur on certain cf-deployments which use alternative login paths other than UAA (this has been resolved in v7.0.2).
v7.0.0
Alert:
There was an issue with the packaging of this initial v7.0.0
release. Please use v7.0.1
instead.
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
Compatibility
Minimum API Version: 3.85.0 (cf deployment v13.5.0)
Change Log
For a detailed overview of v7 and upgrade guide, see https://docs.cloudfoundry.org/cf-cli/v7.html
New Features
- Support for rolling app deployments for
push
,restart
,restage
, andcopy-source
- Support for pushing apps with multiple processes
- Support for pushing apps with sidecar processes
- New command:
create-app
- New command:
packages
- New command:
create-package
- New command:
stage-package
- New command:
droplets
- New command:
set-droplet
- New command:
apply-manifest
- New command:
cancel-deployment
- New command:
labels
- New command:
set-label
- New command:
unset-label
Deprecations
- Dropped all support for DEAs
- Dropped all support for v1 service brokers
- Removed
--hostname
and-d
flags onpush
and associated manifest properties. - Removed
--route-path
and--no-hostname
flags onpush
- Removed
rename-buildpack
command in favor of--rename
flag onupdate-buildpack
command - Removed
--random-port
flag fromcreate-route
andmap-route
commands. This is now the default behavior.
Other Changes
- Most commands have received minor, stylistic changes to improve readability and consistency between commands.
- Errors are output to
stderr
instead ofstdout
- Required flag arguments are now positional arguments
- Optional positional arguments are now flag arguments
cf restage
no longer results in aaudit.app.restage
audit event- Some command names have been updated. The old names are preserved as aliases.
Known Issues
- Windows binary zip files do not include a symbolic link from
cf7 -> cf
due to lack of.zip
support for symbolic links on Windows. - Login does not work in certain non-cf-deployment environments due to inconsistent endpoint behavior.
Contributors
The release of v7 was only possible due to the hard work of folks on the cf CLI team, V3 Acceleration Team, Services API team, and many other teams. Below are a list of some folks from these and other teams that did the hard work to make v7 happen.
Piyali Banerjee, Alexander Berezovsky, Alex Blease, George Blue, Seth Boyles, Connor Braa, Florian Braun, Winna Bridgewater, Andrew Brown, André Browne, Marcela Campo, Abby Chau, Renee Chu, Greg Cobb, Josh Collins, Emina Cosic, Andrew Crump, Brian Cunnie, Tim Downey, Derik Evangelista, Daniel Fein, Oleksii Fedorov, Weyman Fung, Anand Gaitonde, Jenna Goldstrich, Nick Guerette, Leah Hanson, Spencer Hawley, Michelle He, Chris Hendrix, Sannidhi Jalukar, Rob Jones, Mike Kenyon, Aarti Kriplani, Merric de Launey, Joao Lebre, Diego Lemos, Belinda Liu, Georgi Lozev, Will Martin, Felisia Martini, Niki Maslarski, Nikolay Maslarski, Andres Medina, Reid Mitchell, Mona Mohebbi, Magesh Murali Kumar, Will Murphy, Harsha Nandiwada, Supraja Narasimhan, Joseph Palermo, James Palmer, Will Pragnell, Eric Promislow, Zach Robinson, Luan Santos, Simon Seif, Chris Selzo, Alex Shan, Brendan Smith, Henry Stanley, Teal Stannard, Steve Taylor, Aditya Tripathi, Sebastian Vidrio, Thomas Viehman, Nicholas Webb, Sarah Weinstein, Eli Wrenn
We would not be here without our dedicated users, especially their pull requests, issues, and the time given for user interviews and discussions. Your feedback has been invaluable. We look forward to more feedback from y'all as we move forward.
Thank you for using the cf CLI and for being so passionate about our app.
v6.51.0
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
Go 1.13.8
The cf CLI is now build with Golang 1.13.8 story
Bug Fixes
-
Increased resiliency to log cache streaming log loss on foundations with multiple log cache doppler nodes story
-
cf logs --recent lost logs if there are more than 4 MB of logs story
-
cf logs now properly retries getting logs on connection failure to the logging API story
-
Requests to Log Cache were not logged in the same format as other HTTP requests in the cf CLI story
Known Issues
-
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
-
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.
Contributors: Brendan Smith, Andrew Crump, Alexander Berezovsky, Steve Taylor, Eric Promislow, Jenna Goldstrich, Chris Hendrix, Nicholas Webb, Reid Mitchell, Josh Collins
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.