Highlights
- CAPI now defaults to using BPM instead of monit directly for running jobs. To continue with the former behavior, set the
bpm.enabledproperty tofalse. - The Cloud Controller has upgraded to Rails 5, Sinatra 2 and Rack 2.
CC API Version: 2.125.0 and 3.60.0
Service Broker API Version: 2.14
CAPI Release
- BOSH spec incorrectly recommends that the cloud_controller_clock job be scaled to a single instance details
- Document in the nfs_mounter job that it doesn't use bpm intentionally details
- Operator can colocate webdav VM with jobs that scale, for non-prod environments details
- Operator can see that cc_deployment_updater is not updating the database during a BBR operation details
- capi release defaults to use bpm details
- use bpm for rotate_cc_database_key errand details
Cloud Controller
- API client can cancel a deployment that has pre-empted an in-flight deployment. details
- Add tests for updating brokers once multi-service-registration exists details
- As a developer, I can see CC API doc for the
service_instance_sharingflag details - As a developer, I can see CC API docs for the
hide_marketplace_from_unauthenticated_usersflag details - As a developer, I can see the name of the service broker providing each service when fetching services resources details
- As an admin, I can register the same broker twice with different names details
- As an admin, I cannot register a broker that has duplicate information in its catalog details
- As an admin, when I query service usage events, I can see the broker's name and GUID details
- As an authenticated user without read-access to a binding's space, I receive a 403 when fetching service binding parameters details
- Processes that are rolling should be discoverable from the deployment resource details
- Upgrade to Rails 5/Sinatra 2/Rack 2 details
- batch CC database queries for copilot sync details
- Fix cc-route-syncer random failure details
- cloud_controller_clock job should not fail to sync apps and tasks when it gets into unrecoverable states details
Cloud Controller Database Migrations
- 20180921102908_remove_uniqueness_on_index_broker_url_from_service_brokers.rb
- 20180924142348_remove_uniqueness_on_index_unique_id_from_services.rb
- 20180924142407_remove_uniqueness_on_index_unique_id_from_service_plans.rb
- 20180925150440_remove_services_label_provider_index.rb
- 20180927105539_add_broker_name_and_guid_to_service_usage_event.rb
- 20181002165615_create_deployment_processes_table.rb
Pull Requests and Issues
- cloudfoundry/cloud_controller_ng #1091: CC performs orphan mitigation inconsistently details
- cloudfoundry/cloud_controller_ng #1216 (part II): Service Broker Service Updates Require Strict Ordering details
- cloudfoundry/cloud_controller_ng #1216: Service Broker Plan Updates Require Strict Ordering details
- cloudfoundry/cloud_controller_ng #1223: Add service broker name + guid to ServiceUsageEvent details
- cloudfoundry/cloud_controller_ng #1227: Check for nil entries in bulk sync call details
- cloudfoundry/cloud_controller_ng #1229: Fix service broker plan updates requiring strict ordering details
- cloudfoundry/cloud_controller_ng #1231: Rationalise orphan mitigation details
- cloudfoundry/cloud_controller_ng #1236: add batching to Copilot::Sync details
- cloudfoundry/cloud_controller_ng #1238: Add tests for multiple plans and services with identical ids details
- cloudfoundry/cloud_controller_ng #1239: Document 'hide marketplace' and 'service instance sharing' feature flags details