cloudfoundry/capi-release 1.28.0

CAPI 1.28.0

on GitHub

Highlights

• Support for docker images that require credentials to access

CC API Version: 2.82.0 and 3.17.0

Service Broker API Version: 2.11

CAPI Release

Cloud Controller

• API client sees that app health checks are resilient to contentious resources after bridge consumption details
• API client should see 422 when space does not exist or user does not have permissions when creating app details
• As an API client, I can specify docker credentials on a v2 app details
• As an app developer I can run tasks for docker apps stored in a registry that requires authentication details
• As an app developer I can stage and run docker apps stored in a registry that requires authentication details
• BBS client author should be able to obtain the isolation segment for a route when an app in a space with an isolation segment is mapped to the route details
• Bump nokogiri to at least 1.7.1 details
• CF users should need cloud_controller.read scope rather than cloud_controller.write to view isolation segment for org an space details
• Operator can configure keep alive timeouts for nginx fronting CC details
• PM should see there is a foreign key constraint between app and space. details

Stager

• As an app developer I can run tasks for docker apps stored in a registry that requires authentication details

Nsync

• As an app developer I can run tasks for docker apps stored in a registry that requires authentication details

Pull Requests and Issues

• cloudfoundry/cloud_controller_ng #687: Remove deprecated endpoint for loggregator details
• cloudfoundry/cloud_controller_ng #813: Increase ssl_verify_depth for more complex ca ceritficate validation details