v1.20.0

This release corresponds to version 6.47.0 of the CF CLI.

Please see the 6.47.0 release notes for more information.

v1.19.0

This release corresponds to version 6.46.1 of the CF CLI.

Please see the 6.46.1 release notes for more information.

v1.18.0

Accidental release.

Contains the same bits as v1.17.0.

v1.17.0

This release corresponds to version 6.46.0 of the CF CLI.

Please see the 6.46.0 release notes for more information.

v1.16.0

This release corresponds to version 6.45.0 of the CF CLI.

Please see the 6.45.0 release notes for more information.

v1.15.0

This release corresponds to v6.44.1 of the CF CLI.

Please see the v6.44.1 release notes for more information.

v1.14.0

UPDATE: A regression has been detected for this release. The bug affect users using client credentials - logs will not appear for cf push or cf logs.

This release corresponds to v6.44.0 of the CF CLI.

Please see the v6.44.0 release notes for more information.

v1.13.0

Bumps CF CLI to version 6.43.0. Changes in this version include:

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 create-service
• cf enable-service-access
• cf disable-service-access
• cf purge-service-offering
• cf service - now display broker names
• cf marketplace now 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@pivotal.io or #sapi on Cloud Foundry Slack.

Enhancements

• cf curl supports a new --fail flag (primarily for scripting purposes) which returns exit code 22 for server errors story
• Improves cf delete-orphaned-routes such 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

Bug Fixes

Security

• Fixes issue with running cf login in 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

32-bit systems

• 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	HealthCheckTimeout	push
v2	App Instance Status	Disk	create-app-manifest
v2	App Instance Status	DiskQuota	create-app-manifest
v2	App Instance Status	Memory	create-app-manifest
v2	App Instance Status	Memory	create-app-manifest
v3	Process	Health Check Invocation Timeout	v3-set-health-check, v3-get-health-check
v3	Process	Index
v3	Process Instance	Uptime	push, restage, restart, start, app
v3	Task	Sequence ID	tasks, run-task
v3	Job	Code	v3-delete, v3-apply-manifest

Other Bug Fixes

• Updates help text for cf curlstory
• Now refresh tokens work properly whilst using cf curl with V3 CC API endpoints story
• Fixes performance degradation for cf services story
• cf delete-service requires that you are targeting a space story
• cf enable-service access for a service in an org will succeed if you have already enabled access for that service in that org story

Full release notes can be found here

v1.12.0

Bumps CF CLI to version 6.41.0. Changes in this version include:

Space to Space Policy story

Supports a Container to Container feature for cf add-network-policy to enable adding network policies between spaces. Changes include:

• -o and -s flags have been added to the cf add-network-policy and the cf remove-network-policy commands to support adding network policies to a specific organization and space
• the cf network-policies table output has been updated with additional columns to indicate destination space and destination org

Note:

• Users on versions of CC API lower than 3.56.0 may experience some latency due to the fact that the CC API did not support the guids filter param (which we require to display destination org and destination space in cf network policies. Users on versions of CC API greater than 3.56.0 should not experience latency issues.
• This release includes changes to existing output to specify the destination app.

Services-related Refactors

Important Note:

We've discovered that for commands we've refactored previously, the CLI started incorrectly allowing for additional arguments to be passed in commands, which are silently ignored. Moving forward, if you provide additional arguments to a command, the command will fail with a meaningful message. We plan on making a global change in a future major release of the CLI. details

In order to prepare for a upcoming service-related feature, the Services API team in London refactored the following commands.

• cf create-service story
• cf disable-service-access story

User-facing changes include:

Updating output where necessary and flavor text to promote consistently as described in our style guide

Minor Enhancements

• updated cf restage help text and the first line in the command's output to indicate that using this command will cause app downtime story
• updated the cf bind-route-service help text to clarify usage instructions story
• improved an error message for cf create-service-boker to be more helpful when the CC API returns a 502 due to an invalid service broker catalog
• upgraded to Golang 1.11.4 story
• added a short name ue for cf unset-env story
• updated cf marketplace command to include a new broker column to prepare for a upcoming services-related feature which will allow services to have the same name as long as they are associated with different service brokers story

Bugs

• fix for cf enable-service-access -p plan whereby when we refactored the code in CLI v6.41.0 it created service plan visibilities as part of a subsequent run of the command (the unrefactored code skipped creating the service plan visibilities); now the command will skip creating service plan visibilities as it did prior to the refactor story
• updated the cf rename-buildpack help text which was missing reference to the -s stack flag story
• updated help text for when users use brew search cloudfoundry-cli story
• now when you run cf service service-instance for a route service, the route service url appears in the key value table story

Full release notes can be found here

v1.11.0

Bumps CF CLI to version 6.41.0. Changes in this version include:

Assign a Stack to a Buildpack epic

Supports the ability to assign a stack to a buildpack that is missing stack metadata. See official documentation for more details.

Important Note: It's important to note that once you assign a stack to a buildpack, you cannot undo the action unless you have access to your buildpack bits.

Additional notes:

• If you have two buildpacks with the same name, and one has a stack associated, and the other has a nil stack; when you run cf update-buildpack buildpack-name --assign-stack stack - the buildpack with nil stack will be updated.

Service Discovery epic

With app service discovery, apps pushed to Cloud Foundry can establish container-to-container communications through a known route. This allows front end apps to easily connect with back end apps.

Now users can use cf create-shared-domain internal.com --internal to create an internal route, and domains has been updated to include a new details column to let users know if a route is internal.

See official documentation for more details.

Refactors

Important Note:

We've discovered that for commands we've refactored previously, the CLI started incorrectly allowing for additional arguments to be passed in commands, which are ignored silently. Moving forward and starting with these refactored commands, if you provide additional arguments to a command, the command will fail with a meaningful message. [details](https://www.pivotaltracker.com/story/show/162259630]

Note we intend to fix this bug for all refactored commands in a major CLI release see additional details

Services-related Refactors

In order to prepare for a upcoming service-related feature, the Services API team in London refactored the following commands. Big thanks to the SAPI team for providing this work to us.

• marketplace story
• create-service-broker story
• enable-service-access story

User-facing changes include:

• Updating output where necessary and flavor text to promote consistently as described in our style guide

Create-shared-domain Refactor

In order to prepare for the Service Discovery (Container to Container Networking feature), we've refactored cf create-shared-domain.
story

User-facing changes include:

• Updating output where necessary and flavor text to promote consistently as described in our style guide

Built with Golang 1.11.x story

Updated to Golang 1.11. See the Golang release summaries for details on the bug fixes.

Enhancements

• updated cf --help to include the delete command story

Full release notes can be found here.