Important
- The way that resources are stored for resource matching has changed. Resource files are now stored in a subdirectory, named
app_bits_cache, in the resource bucket . This means existing resource files will be orphaned. This change is in preparation for automated orphan cleanup for Cloud Controller managed blobstores. If storage space is a concern for a given environment, then operators should consider manually purging the resource bucket after this release is deployed. Before purging the resource bucket, please ensure that resources are stored in a different bucket than all other resources (droplets, packages, buildpacks).
Highlights
- Introduces support for Service Broker API 2.12
- Resolves several issues when syncing LRPs and Tasks with Diego
CC API Version: 2.85.0 and 3.20.0
Service Broker API Version: 2.12
CAPI Release
Cloud Controller
- API Client can delete an app asynchronously details
- API Client experiences improved performance of
GET /v3/app/<guid>/tasksdetails - API client can discover how to allow all types and codes for ICMP security group rules. details
- API client can discover link for
/v3/processesdetails - API client can discover the logging api location details
- API client should NOT receive error when canceling a task diego does not know about details
- API client should follow a consistent schema to specify an service-binding-to-app relationship when creating a service binding details
- API client should not be able to specify custom buildpacks for an app when platform has disabled custom buildpacks details
- API client should not be able to use custom buildpacks when the platform has disabled custom buildpacks details
- API client should see that next_url does NOT omit the organization_guid filter for /v2/routes details
- App developer should be able to specify HTTP Healthcheck for processes using the v3 api details
- CC Sync job fails when app has shared domain with
router_group_guiddetails - Do not fail sync when there is a race condition creating LRPs details
- With many processes, if the first one fails due to invalid LRP, freshness will still be bumped even if there is another error details
Pull Requests and Issues
- cloudfoundry/cli #1096:
cf pushfails when file mode is invalid, but doesn't say which file was the cause details - cloudfoundry/cloud_controller_ng #821: When calling /v2/spaces/:spaceGuid/services, space-scoped services return an empty array for their service plans details
- cloudfoundry/cloud_controller_ng #831: Misleading documentation for Resource Match API ? details
- cloudfoundry/cloud_controller_ng #835: Support Open Service Broker API v2.12 details