Skip to content

v1.13.0

Choose a tag to compare

View all tags
@tjvman tjvman released this 21 Feb 18:48
v1.13.0
ee99851

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 [email protected] 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

Assets 2
Loading