Highlights
- V3 Domains and Droplets are now GA
- Async service bindings are now GA
- Creating, listing and getting a service broker is now supported in V3 as experimental endpoints
- Upgrading individual service instances is now possible through the API if brokers support it
- Rate limiter now correctly limits clients
CC API Version: 2.137.0 and 3.72.0
Service Broker API Version: 2.14
CAPI Release
- API client can upload bits for a droplet details
- Add capi-release BOSH property to disable remaining non-TLS ports details
- Enforce that Cloud Controller must always be configured to support a TLS-protected endpoint (default configuration of Cloud Controller) details
Cloud Controller
- API User can filter routes by space_guid details
- API client can delete a route details
- API client can filter routes details
- API client can list routes details
- API client can upload bits for a droplet details
- API client can see audit events for droplet upload on the v3 API details
- API client can see audit events for route delete on the v3 API details
- API client can see a link to the upload endpoint for a droplet details
- API client can see when uploading bits fails for a droplet details
- API user can filter domains by guid details
- API client should NOT see manifest field names in API endpoint errors details
- API error message is unclear for uploading droplet with empty tgz file details
- As a developer, I can see the maintenance_info on each service instance and each service plan when fetching a space summary details
- As a platform engineer I can see the maintenance_info for a service instance details
- As a service broker author, when a plan change is requested for a service instance, I receive maintenance_info of the new plan in the PATCH request details
- As a v7 CLI admin user I can register a global service broker without using v2 endpoints details
- Async bindings features should be GA'd details
- Maintenance info structure should be validated by CC according to the spec details
- Mark the service_brokers link as experimental in the /v3 root resource details
- Space scoped service broker representations should contain links to the associated space details
Cloud Controller Database Migrations
Pull Requests and Issues
- cloudfoundry/cloud_controller_ng #1326: Suggest unauthenticated rate-limited users log in details
- cloudfoundry/cloud_controller_ng #1340: Add internal api docs details
- cloudfoundry/cloud_controller_ng #1341: Delete critical file details
- cloudfoundry/cloud_controller_ng #1343: Suspended organizations not visible to SpaceDevelopers on v3 details
- cloudfoundry/cloud_controller_ng #1346: Mark the service_brokers link as experimental in v3 details
- cloudfoundry/cloud_controller_ng #1347: fix passing application env vars to eirini details
- cloudfoundry/cloud_controller_ng #1348: V3 service brokers contain a link to the associated space details
- cloudfoundry/cloud_controller_ng #1349: Add maintenance_info to the service_instance and enable update details
- cloudfoundry/cloud_controller_ng #1355: Add maintenance info in space summary endpoint details
- Investigate empty "actee" in
audit.user.organization_user_addaudit events details - Rate limiter treats client authenticated users as being unauthenticated details
- capi release only uses bpm to run processes details
- ccng_monit_http_healthcheck can interfere with bbr workflows details
- cloudfoundry/capi-release #140: pre-backup-lock/post-backup-unlock scripts are not idempotent details
- Fix cascading failures caused by monit /v2/info healthcheck restarts details
- Incorrect error message when stopping a deploying app details