cloudfoundry/capi-release 1.83.0

CAPI 1.83.0

on GitHub

Highlights

• VCAP_APPLICATION environment variables now include org guid, org name, process type and process_id
• Annotations key and prefix now conform to same format as K8s annotations metadata
• Service Instance parameter fetching is GA
• Maintenance info descriptions now appears on service plans and service instances

CC API Version: 2.138.0 and 3.73.0

Service Broker API Version: 2.14

CAPI Release

• Co-pilot consumes VIPs from CAPI details
• Enable array format for encryption keys in yml config details
• Operator can rotate db encryption keys details
• Pipeline: Investigate 404s from the API during SITS details
• Update capi-workspace and local repos to use Ruby 2.5.5 details
• Use an endpoint other than /v2/info as the health check details
• cloudfoundry/capi-release #144: add internal_route_vip_range to cc route syncer job details
• cloudfoundry/capi-release #145: Add Eirini mTLS properties to CC clock and worker details

Cloud Controller

• API client add, modify, and remove metadata on a route details
• API client can insert one or more destinations for a route details
• API client can remove a destination from a route details
• API client can replace all destinations for a route details
• API client can view destinations for a route details
• API client can get the full URL for a route details
• API client can query routes with label_selector details
• API client can see audit events for route mapping on the v3 API details
• API client can see audit events for route unmapping on the v3 API details
• API client can see a link to destinations for a route details
• API user can atomically delete unmapped routes details
• Add audit event for cancelled deployment details
• Add organization_id and organization_name to VCAP_APPLICATION environment variables details
• Add process_id and process_type to VCAP_APPLICATION environment variables details
• As a broker author, I receive maintenance_info in the previous values structure on an update request for an instance details
• As a broker author, I want the platform to quickly reject my registration, if I have extra fields in my maintenance_info object details
• As a ccv3 client, when I create a service broker with a URL that doesn't serve a catalog, the operation should fail without debris details
• As a v7 CLI user I want to get warnings when I create a service broker that adds a volume or route service, but this is disabled in the CF config details
• As an API consumer, I can see the description of a maintenance associated associated with service instances and plans on the space summary details
• As an API consumer, I can see the description of a maintenance associated with a service plan and service instance details
• As an API consumer, any maintenance version I request that is different from the current version, should be forwarded to the broker details
• As an API consumer, if I request maintenance that the instance has already performed, it should not call the broker details
• As an API user, if I request maintenance that the broker thinks is in conflict, I should get a useful error details
• Broker rejection of UNBIND during async BIND untested behaviour details
• Broker rejection of delete during async SI creation untested behaviour details
• Create /v3/spaces with no relationships argument results in a 500 details
• Create an Architectural Decision Record (ADR) describing our plan for handling annotations with long key names details
• Create service broker flow should support authentication types beyond basic details
• Create space audit events (audit.space.create) using V3 apis details
• Make parameter fetching GA details
• Registration of a service broker in v3 should provide useful validation details
• See if completed task pruning can be made more performant details
• Service instance sharing events should not be experimental details
• Update Annotation key to use K8s key conventions details
• Update capi-workspace and local repos to use Ruby 2.5.5 details
• Use an endpoint other than /v2/info as the health check details

Cloud Controller Database Migrations

• 20190531214252_create_route_metadata_tables.rb
• 20190617170734_add_key_prefix_to_package_annotations.rb
• 20190617175452_add_key_prefix_to_buildpack_annotations.rb
• 20190617181003_add_key_prefix_to_droplet_annotations.rb
• 20190617181111_add_key_prefix_to_app_annotations.rb
• 20190617181159_add_key_prefix_to_revision_annotations.rb
• 20190617181245_add_key_prefix_to_task_annotations.rb
• 20190617181325_add_key_prefix_to_process_annotations.rb
• 20190617181421_add_key_prefix_to_isolation_segment_annotations.rb
• 20190617181509_add_key_prefix_to_stack_annotations.rb
• 20190617181730_add_key_prefix_to_service_instance_annotations.rb
• 20190617181810_add_key_prefix_to_deployment_annotations.rb
• 20190617181849_add_key_prefix_to_domain_annotations.rb
• 20190617181924_add_key_prefix_to_space_annotations.rb
• 20190617182113_add_key_prefix_to_organization_annotations.rb
• 20190617182135_add_key_prefix_to_build_annotations.rb
• 20190617182203_add_key_prefix_to_route_annotations.rb

Pull Requests and Issues

• Invalid service metadata should not break the marketplace details
• cloudfoundry/cloud_controller_ng #1361: Cloud Controller now sends its VIPs to copilot details
• cloudfoundry/cloud_controller_ng #1364: Allow cancel deployment to make a FAILING deployment CANCELED details
• cloudfoundry/cloud_controller_ng #1366: Reject maintenance_info with extra keys details
• cloudfoundry/cloud_controller_ng #1368: Validation for metadata.shareable on the service broker catalog details
• cloudfoundry/cloud_controller_ng #1369: Upgrade v3 docs favicon to be web 3.0 compatible details
• cloudfoundry/cloud_controller_ng #1370: [Documentation] Fix Broken Links details
• cloudfoundry/cloud_controller_ng #1371: Add maintenance_info description to instances and plans details
• cloudfoundry/cloud_controller_ng #1373: Large spike in database read operations during bulk event deletion details
• cloudfoundry/cloud_controller_ng #1375: Creating apps with emoji names results in a 500 details
• cloudfoundry/cloud_controller_ng #1382: UaaClient caches invalid tokens for service broker related workflows details