You can use Cloud Foundry Command Line Interface (cf CLI) v8 to interact with Cloud Foundry API (CAPI) V3. This topic describes the major changes between cf CLI v7 and cf CLI v8.
The cf CLI development team aims to provide:
A seamless upgrade experience from cf CLI v7. Changes are minimal. Where there are changes, the team has incorporated feedback from the community to simplify the cf CLI user experience.
Details about potential breaking changes and alternative workflows for scripting environments.
To understand the differences between specific commands, see Command differences below.
For more information about CAPI V3, see the CAPI V3 documentation.
For more information about cf CLI v8, see v8.0.0 in GitHub.
Some key new features available through the cf CLI v8 are:
To install cf CLI v8, see the README in the Cloud Foundry CLI repository on GitHub. It includes instructions for downloading the latest CAPI release candidate, which is what the cf CLI v8 beta is tested against.
In cf CLI v8, Golang has been updated from v1.13 to v1.16. When targeting a foundation that does not have a SAN, you might encounter errors because the common name field is deprecated in Golang v1.15 and later. For more information, see X.509 CommonName deprecation in the Golang v1.15 release notes.
The cf CLI v8 requires cf-deployment v16.11.0 or later.
This version of cf-deployment contains CAPI release v1.109.0, which provides the CAPI V3 API v3.99.0.
For more information, see the cf CLI Versioning and Support Policy on GitHub.
These sections describe changes in commands from cf CLI v7 to cf CLI v8. They also provide important information for those who use the cf CLI in scripts.
For information about possible breaking changes, see the Table of differences below. This table includes removed flag options, updated output, and removed or changed argument requirements.
When you apply a manifest by running cf push
, cf CLI v8 does not provide a manifest diff through the V3 manifest diff endpoint. This new endpoint supports version 1 manifests only. For more information, see Create a manifest diff for a space (experimental) in the CAPI documentation.
If you have scripts that rely on the cf CLI, this section describes possible changes in cf CLI v8 that might affect scripts.
Some of these changes are:
--wait
flag.The table below summarizes how commands differ between cf CLI v7 and cf CLI v8.
Command | Changes |
---|---|
cf bind-service |
|
cf bind-route-service |
|
cf create-service |
|
cf create-service-key |
|
cf delete-service |
|
cf delete-service-key |
|
cf map-route |
|
cf marketplace |
|
cf route |
|
cf routes |
|
cf service |
|
cf service-key |
|
cf services |
|
cf unbind-service |
|
cf unbind-route-service |
|
cf update-service |
|
cf upgrade-service |
|