Highlights
- Operators should begin deploying without the legacy Cloud Controller Bridge translation components. This document provides additional information.
- Introduce support for multiple buildpacks.
- Resolve issue where TASK_STOPPED usage events were not recorded for an app that was deleted with in-flight tasks.
CC API Version: 2.90.0 and 3.25.0
Service Broker API Version: 2.12
CAPI Release
Cloud Controller
- API client can request an app or build with lifecycle including multiple buildpacks details
- API client can successfully stage a droplet with multiple buildpacks details
- API client can cancel a task using POST with a /actions url details
- API client can observe failure reason for a job details
- API client can scale a process using POST with a /actions url details
- API client can start an app using POST with a /actions url details
- API client can stop an app using POST with a /actions url details
- API client does NOT see stage link details
- API client sees TASK_STOPPED app_usage_event when the parent app is deleted and the task is still running details
- Can't update environment variables with v3 api when app has no existing environment variables details
- Loggregator can check log access using mtls details
- ProcessSyncer should not fail to update freshness when attempting to update a LRP that no longer exists (race condition) details
- Stopping our clock job should not timeout details
Pull Requests and Issues
- cloudfoundry/capi-release #48: /v2/spaces/<SPACE_GUID>/security_groups returns duplicate entries details
- cloudfoundry/cloud_controller_ng #843: Error when using long Docker Registry passwords details
- cloudfoundry/cloud_controller_ng #848: Missing indexes for some SELECT queries, which are frequently executed by CC details