github cloudfoundry/capi-release 1.54.0
CAPI 1.54.0

latest releases: 1.134.0, 1.133.0, 1.132.0...
6 years ago

Important

This release removes the ability to configure temporary flags used to opt into secure CC and Diego communication. Prior to deploying this release, ensure these instructions have been completed, otherwise API downtime will occur.

As part of this work, we have removed the following components from capi-release

  • stager
  • nsync
  • tps listener

Highlights

  • Per invocation timeouts for http and port health checks are configurable on processes
  • The experimental feature -- server side manifests -- has parity with cli manifests
  • Fixed an issue causing duplicate app usage events for STOPPED and STAGING_STOPPED
  • Bumped cloud controller dependencies

Notable bumped dependencies

  • fog-aws (1.4.1 -> 2.0.1)
  • fog-google (1.2.0 -> 1.3.3)
  • fog-local (0.3.1 -> 0.5.0)
  • pg (0.19.0 -> 1.0.0)
  • mariadb_connector_c (2.3.0 -> 2.3.5)
  • nginx (1.13.4 -> 1.13.12)

CC API Version: 2.108.0 and 3.43.0

Service Broker API Version: 2.13

CAPI Release

  • Operator can no longer configure temporary bridge tls properties details
  • Operator can no longer deploy deprecated bridge components in capi-release details

Cloud Controller

  • API client can view all buildpacks used to stage a droplet details
  • API client can configure per invocation timeout for http health checks details
  • API client can configure per invocation timeout for port health checks details
  • API client can include space in an app response details
  • API client can set environment variables using a manifest details
  • API client can set health check endpoint using a manifest details
  • API client can set health check timeout using a manifest details
  • API client can set health check type using a manifest details
  • API client can set no-route using a manifest details
  • API client can set random-route using a manifest details
  • API client can set routes using a manifest details
  • API client can set service bindings using a manifest details
  • API client sees that the 'name' parameter is not experimental in the api docs for service bindings details
  • As a dev, I see a warning when providing configuration params when creating a service binding for a user-provided service instance details
  • Duplicate STOPPED and STAGING_STOPPED App Usage Events details

Pull Requests and Issues

  • cloudfoundry/cloud_controller_ng #1120: Add documentation of undocumented query details
  • cloudfoundry/cloud_controller_ng #1050: Add retry logic when assigning a random port details
  • cloudfoundry/cloud_controller_ng #1107: 500 Unknown error on /v2/spaces/GUID/summary while apps are being deleted details
  • cloudfoundry/cloud_controller_ng #1119: Undocumented query parameter for 'GET /v2/organizations/:guid/user_roles' details
  • cloudfoundry/cloud_controller_ng #1120: Add documentation of undocumented query details
  • cloudfoundry/cloud_controller_ng #1124: Parallel DELETE /v2/apps/guid on same app result in 204/500 instead of 204/404 details

Don't miss a new capi-release release

NewReleases is sending notifications on new releases.