CC API Version: 2.65.0 and 3.0.0
Service Broker API Version: 2.10
CAPI Release
- Bumped to Golang 1.7
Cloud Controller
- As a Cloud Controller client, I would like to present a UAA token with
cloud_controller.userscope to determine if the user has access to sensitive information and/or insensitive information about an application details - Buildpacks should not be supplied to Diego if the blob doesn't exist details
- Cloud Controller should protect against a broker that doesn't return credentials details
- Add retry logic around FogBlob and DavBlob details
- Cloud controller should fail more gracefully when blobs are missing or the blobstore is misconfigured. details
- Add clearer documentation for seeding vs modifying/creating security groups details
- All V3 Resources have an updated_at timestamp upon creation instead of null details
- Admin read only cannot
curl /v2/spaces/:guiddetails - Read-only admin users get unknown error when getting v2 apps details
Pull Requests and Issues
- cloudfoundry/cloud_controller_ng#699: Make service plans queryable by id provided by the service broker details
- #34: Cloud Controller ctl script should not restart directly the consul_agent details