Highlights
- Added ability to define minimum required memory for a sidecar - allows sidecars to work with java apps
- Updated status reporting for deployments - now includes more granular status. The deployment
statevalue is now DEPRECATED. Please use deployment status instead.
CC API Version: 2.139.0 and 3.74.0
Service Broker API Version: 2.15
CAPI Release
- cloudfoundry/capi-release #148: Consume file-server link with HTTPS URL details
- New array encryption key format should support an empty array details
- As a CF operator, I expect that cloud controller generates https urls to file-server assets via a BOSH link from the file-server so I can be sure communication paths in my foundation are secure details
Cloud Controller
- API client can filter resources by empty string values details
- API client can filter resources by null values details
- API client can list routes mapped to an app details
- API client can add destinations to a route with weights 🏋🏾♀️ details
- API client can no longer use v3 route mappings details
- API client can see documentation for destination objects details
- API client can see documentation for destination insertion and replacement details
- API client can see weights in audit events for mapping and unmapping routes details
- API user can atomically delete unmapped routes details
- API user can see if matching routes exist for a domain details
- Add memory to the sidecar POST/GET/PATCH endpoints details
- Add memory to the sidecar in app manifest details
- Add query param to app list endpoint to filter by app stack details
- Add sidecar memory min requirement for sidecar app manifest details
- As a CLI admin or space developer user I can register a space scoped service broker without using v2 endpoints details
- As a CLI user, if I request an upgrade but the broker doesn't support it, I should get a useful error details
- As a Platform Engineer, I can trace requests from the platform to the service broker details
- As a broker author, I should receive maintenance_info on a service instance provision details
- CC supports OSBAPI v2.15 details
- Client developer sees last successful health check for a rolling deployment details
- Client developer views status for a rolling deployment details
- Deployment status should be queryable details
- Process memory cannot be below sum of sidecar memory details
- Update Ruby version for Travis CI to 2.5.5 details
- Update annotations section in docs to reflect annotations key/prefix details
Cloud Controller Database Migrations
- 20190628183006_change_default_route_mapping_weight_to_null.rb
- 20190701233808_add_memory_column_to_sidecars.rb
- 20190711205517_add_value_and_reason_status_to_deployments.rb
- 20190712210940_backfill_status_for_deployments.rb
- 20190716215540_add_status_indices_to_deployments.rb
Pull Requests and Issues
- Investigate occasional 500 when creating a deployment details
- Investigate weird buildpack creation behavior (deadlocks and multiple buildpacks getting same position) details
- v3-apply-manifest PollableJobs dont seem to update updated_at when their states change details
- cloudfoundry/cloud_controller_ng #1384: Filtering service plans by service broker id results in CF-DatabaseError details
- cloudfoundry/cloud_controller_ng #1389: Bump lodash from 4.17.11 to 4.17.14 in /docs/v3 details
- Look into Travis CI failures details