cloudfoundry/capi-release 1.94.0

CAPI 1.94.0

on GitHub

DO NOT USE
This release contains a bug that can trigger service instance data loss.

Highlights

• Resolved issue with rolling deployments not working properly on Windows

CC API Version: 2.149.0 and 3.84.0

Service Broker API Version: 2.15

CAPI Release

• cloudfoundry/capi-release #168: Package ruby-2.4.6-r0.9.0 obsolete details
• cloudfoundry/capi-release #169: Add config parameter for new logging.anonymize_ip flag in CC details
• Fix CI by bumping golang components of capi-release to 1.14 details

Cloud Controller

• API client can filter routes by mapped app guids details
• API client can assign router groups to v3 domains details
• API client can see a link to a domain's router group details
• API client can view a route's protocol details
• API client receives helpful messages when CC has difficulty talking with Routing API when interacting with domains. details
• API client sees an error when creating a route with a host or path for a TCP domain details
• API clients can see what protocols are supported by a domain details
• Explore: do we need an available flag and status for /v3/service_brokers details
• UnknownError ⁉️ when API user specifies big numbers for total_instances limit details
• Users with hax0r guids should not break the API details
• v3 API && v7 CLI Remove the state from service brokers API and CLI response details
• v3 Correct actor in audit event logs for deletion of service offering and service-plan details
• v3 Ensure that it’s not possible to create SI for non-available broker details
• v3 Error responses when creating SI should include error message only once details
• v3 Get name of service broker in service offering request details
• v3 Get name of service broker in service plan request details
• v3: Respect plan max_polling_duration defined in broker catalog details
• v3: Warns when required permissions are no longer available when creating a MSI details
• v3: Update a user provided service instance details
• Alana can observe route CRDs created when a route is mapped details
• Alana can observe updates to mapped-routes by looking at Route CRDs details
• Alana can verify that a deleted CF route does not exist in K8s details
• Env variables defined by app developer can be passed along to kpack during build details
• cf7 push should work on cf-for-k8s without having to enable diego_docker feature flag details

Cloud Controller Database Migrations

• 20200507224709_change_crash_events_exit_description_to_text.rb

Pull Requests and Issues

• 500s appearing in cc_worker logs: undefined method id for NilClass details
• error messages should say "cannot" rather than "can not" details
• cloudfoundry/capi-release #152: Very large event meta-data on crash events causes DB issues details
• cloudfoundry/capi-release #162: App events with large meta-data are cause DB error and are not recorded in event table details
• cloudfoundry/capi-release #166: ccng_monit_http_healthcheck doesn't fail on status >=400, /healthz is rate limited details
• cloudfoundry/cloud_controller_ng #1572: /v2/apps//summary does't return newly set env var unless app is restarted. details
• cloudfoundry/cloud_controller_ng #1604: Ignore updates of buildpack (e.g. second cf push) details
• cloudfoundry/cloud_controller_ng #1605: Warning field missing from Jobs documentation details
• Rolling deployments don't work on Windows cells details