Highlights
- Resolves several issues when removing legacy bridge components.
- Now compatible with NFS
- Now works with service bindings that include volume services
Job Spec Changes
properties.uaa.clients.cc_service_key_client.secret: This release introduces a new UAA client. Operators must provide a client secret. Any sufficiently strong password-like string will suffice.properties.uaa.clients.cc-service-dashboards.secret: capi-release 1.42.0 includes a regression that marked the previously optional properties.uaa.clients.cc-service-dashboards.secret property as required. Temporarily set this property to any strong password if you haven't already provided a value. The next capi-release will again mark this property as optional.
CC API Version: 2.96.0 and 3.31.0
Service Broker API Version: 2.12
CAPI Release
- cf-deployment can deploy windows2016 and windows2012R2 cells details
Cloud Controller
- API client can discover if SSH is enabled for an app details
- API client can enable/disable the SSH feature for an app details
- API client observes proper pagination links when viewing app features details
- App logs do not get emitted from CC workers/CC Clock details
- As a CTA I have documentation on the schema work in the CAPI documentation details
- As a SBA I can see the Originating Identity HTTP header on all requests details
- As a SBA, I want to receive a context object when creating a service binding details
- As an SBA, I can register a schema using either draft 4 or draft 6 details
- Spec files only contain meaningful properties for their jobs details
- cf push with stack and instance_count fails. details
- stop leaking pre-start processes details
Pull Requests and Issues
- cloudfoundry/cloud_controller_ng #883: cf ssh broken for docker containers that don't expose a port details
- cloudfoundry/cloud_controller_ng #892: volume services broken if nsync not available on cc_bridge details
- cloudfoundry/cloud_controller_ng #893: Fog nfs local blobstore not compatible with tls details