Highlights
- Buildpacks can be associated to a specific stack
- Rolled azure fog client back, to prevent slow push times
- Experimental support of asynchronous service bindings
CC API Version: 2.112.0 and 3.47.0
Service Broker API Version: 2.13
CAPI Release
Cloud Controller
- API client can find docs for include parameter details
- API client can retrieve current manifest details
- API client can see that creating a deployment results in multiple web-ish processes for the associated app details
- API client can view json example next to object definitions in v3 docs details
- API client connection does not hang when UAA is unavailable details
- API client receives useful error when setting buildpack properties on a docker app details
- API client sees that origin field is not experimental in docs and old remove endpoints are deprecated details
- API client should be able to specify 'null' for buildpack in their manifest to autodetect the buildpack for their app details
- API client should not see incorrect field name for buildpack errors details
- API client should receive the same error creating a build when the package does not exist or client lacks access to the package details
- API client should see meaningful error when trying to map a route for a non-existing domain using a manifest details
- Add index to
stateon packages details - As a CC user, I am able to associate buildpacks with stacks details
- As a CF app developer, I expect the instance-identity credentials certificate also to include the org and space guids so that I can use them to satisfy broader CF authorization predicates details
- As a developer, I can asynchronously bind a syslog_drain_url binding details
- As a developer, I can asynchronously bind a volume_mounts binding details
- As a developer, I can fetch a service binding and see that a create operation failed because the broker did not return a valid binding details
- As a developer, I can fetch a service binding and see that a create operation has failed/timed out details
- As a developer, I can fetch a service binding and see that a create operation has succeeded details
- As a developer, I can fetch a service binding and see that there is a create operation in progress details
- As a developer, I can fetch a service binding that has been created synchronously and see that the create operation completed successfully details
- As a developer, I can make a service binding create request with accepts_incomplete=false and receive a 422 Not Supported details
- As a developer, I can make a service binding create request with accepts_incomplete=true and receive a 201 details
- As a developer, I can make a service binding create request with accepts_incomplete=true and receive a 202 details
- As a developer, I see an error if I try to create a service binding which has a create operation in progress details
- As a developer, I see an error if I try to delete a service binding which has a create operation in progress details
- CC documentation show accepts_incomplete for service binding as an experimental feature details
- Fetch service instance/bindings returns string keyed hashes instead of symbols details
- Investigate azure blobstore issues details
- Move database calls out of PaginatedListPresenter details
- Operator can disable deployment resources details
- Repeated requests to v3 endpoints result in too many open statsd connections (and thus failed requests and/or crashed CCs) details
- Threads that are killed when an error occurs during sync may not release their db connection details
- UAA connection timeout is configurable and has a relaxed default details
- We should log an audit event for async operations even if user is deleted details