github cloudfoundry/capi-release 1.65.0
CAPI 1.65.0

latest releases: 1.134.0, 1.133.0, 1.132.0...
pre-release6 years ago

Investigating a potential regression

Highlights

  • Support for Open Service Broker API 2.14
  • Service instance sharing is GA
  • Resolve issue that causes some apps to go into a crashing state following a deployment.

CC API Version: 2.119.0 and 3.54.0

Service Broker API Version: 2.14

CAPI Release

  • Operator can configure capi-release to perform BBR operations using TLS when speaking to the database details
  • rotate_cc_database_key errand fails when CC->DB TLS is enabled details

Cloud Controller

  • Documentation Service instance shared_to should contain space_guid details
  • API client can understand how a command is applied to a process now that manifest can provide one details
  • API client observes that the duration of an app deployment does not change when other deployments happen concurrently details
  • As a CF developer, I can delete a service binding using the recursive=true flag on the service instance delete endpoint details
  • As a CF developer, I can unshare a service instance and see that service bindings are deleted asynchronously details
  • As a developer, I can delete a service binding asynchronously and see that the binding is deleted details
  • As a developer, I can delete a service binding asynchronously and see the binding information in the response details
  • As a developer, I can fetch a service binding and see that an unbind operation has failed/timed out details
  • As a developer, I can fetch a service binding and see that there is a delete operation in progress details
  • As a developer, I can make a service binding delete request with accepts_incomplete=false and receive a 422 Not Supported details
  • As a developer, I can make a service binding delete request with accepts_incomplete=true and receive a 202 details
  • As a developer, I can make a service binding delete request with accepts_incomplete=true and receive a 204 details
  • As a developer, if I try to delete a service binding with accepts_incomplete=false and the broker starts an asynchronous operation, I see a warning details
  • As a service author, when I return an invalid binding after an asynchronous bind, I do not receive an automatic unbind request details
  • As a service author, when I return an invalid binding, an asynchronous unbind request is automatically sent to the broker details
  • As an admin, I see an error if I try to delete a space that has a binding operation in progress details
  • Brokers returning 410 to last_operation during create binding operations should be considered invalid and CC should continue polling details
  • CC documentation show accepts_incomplete for deleting a service binding as an experimental feature details
  • CC supports OSBAPI v2.14 details
  • Fix CC->DB TLS when using MySQL details
  • List all service bindings for unknown service instance returns 500 instead of 404 details
  • Support new "/packages with resources json" in v2 API, i.e. when CC talks to Bits-Service details

Cloud Controller Database Migrations

Pull Requests and Issues

  • cloudfoundry/cloud_controller_ng #1184: Extend cp_to_blobstore with resources param details
  • cloudfoundry/cloud_controller_ng #1185: Users can delete service bindings asynchronously details
  • cloudfoundry/cloud_controller_ng #1187: Listing all service bindings for unknown service instance returns 500 instead of 404 details
  • cloudfoundry/cloud_controller_ng #1192: Fix flaky test in service instance delete action details
  • cloudfoundry/cloud_controller_ng #1195: Add missing fields to shared service docs examples details
  • cloudfoundry/cloud_controller_ng #1199: CC should continue polling last_operation on 410 from the broker in case of binding create details

Don't miss a new capi-release release

NewReleases is sending notifications on new releases.