cloudfoundry/capi-release 1.68.0

CAPI 1.68.0

on GitHub

Highlights

• Resolve issue that causes buildpacks with the same name, but different stacks fail to install

CC API Version: 2.122.0 and 3.57.0

Service Broker API Version: 2.14

CAPI Release

• As a CF operator, I expect each tps-watcher instance to be able to reclaim its locket lock if it unexpectedly crashes without releasing the lock details
• Remove unused template from capi-release details
• Upgrade bundler in capi-release to 1.16.x details

Cloud Controller

• API client can cancel a deployment details
• API client can filter deployments by state details
• API client can specify a droplet when creating a deployment details
• API client receives meaningful error if app does not have a current droplet when creating a deployment details
• Add deployments link to /v3 endpoint details
• As a developer, I can see the OSBAPI version CF supports using the /v2/info endpoint details
• CC can use log cache to retrieve container metrics for apps with > 1000 instances details
• DB Encryption Key Rotator does not properly rotate rows with NULL encryption key labels details
• Deadlock error when creating two buildpacks simultaneously details
• Race condition during buildpack upload can cause buildpack uploading to fail details
• Scaling memory through apply-manifest restarts app details

Cloud Controller Database Migrations

• 20180828172307_add_previous_droplet_to_deployments.rb
• 20180904174127_add_original_web_process_instance_count_to_deployments.rb
• 20180904210247_add_index_to_deployments_on_state.rb