Skip to content

CAPI 1.95.0

Pre-release
Pre-release
Compare
Choose a tag to compare
@capi-bot capi-bot released this 11 Jun 23:16
1.95.0
ae31aea

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

Highlights

CC API Version: 2.150.0 and 3.85.0

Service Broker API Version: 2.15

CAPI Release

Cloud Controller

  • API client author can see information in the upgrade guide about how to use audit events on v3 details
  • API client author can see information in the upgrade guide about how to use usage events on v3 details
  • API client author can see information in the upgrade guide about what happened to v2 summary endpoints and how to upgrade away from them on v3 details
  • API client can clear the buildpack cache details
  • API client can discover app usage events on the v3 API details
  • API client can discover service usage events on the v3 API details
  • API client can discover usage events on the v3 API details
  • API client can download droplets on the v3 API details
  • API client can filter routes by port on the v3 API details
  • API client can filter app usage events details
  • API client can filter service usage events details
  • API client can filter usage events details
  • API client can list app usage events details
  • API client can list service usage events details
  • API client can list usage events details
  • API client can purge and reseed app usage events (create an epoch) details
  • API client can purge and reseed service usage events (create an epoch) details
  • API client can see data for a service usage event details
  • API client can see data for an app usage event details
  • API client can view a service usage event details
  • API client can view a service usage event details
  • API client can view an app usage event details
  • API client can view an app usage event details
  • API client can can filter app usage events using after_guid details
  • API client can can filter service usage events using after_guid details
  • API client can create a route with a port on the v3 API details
  • API client can create a route with a random port on the v3 API details
  • API client can see links on usage events details
  • API client can see permissions for an app details
  • API client can see a global summary of memory and instance usage across the whole platform details
  • API client receives helpful messages when CC has difficulty talking with Routing API when interacting with routes. details
  • API client sees an error when creating a route with a host or path for a TCP domain details
  • API client should NOT see download link for droplets with docker lifecycles details
  • API client should see a helpful error when attempting to download a droplet with a docker lifecycle details
  • API make MySQL unit tests less flaky details
  • API user should be able to check routes with ports details
  • Charter: Make sure there are no other ways for the routing API to betray us [Time Box: 1 Day] details
  • Downloading droplets is not experimental in the api docs and link details
  • TCP Routes are not experimental in the API docs details
  • v3 Can't create service instance when service broker was created with v2 details
  • v3 Fix pagination link for that includes fields query param details
  • v3 GA v3 service brokers details
  • v3 GA v3 service offerings details
  • v3 GA v3 service plan visibility details
  • v3 GA v3 service plans details
  • v3 Respect catalog's plan_updateable property details
  • v3 Service broker URL exposed when the broker errors during SI provision details
  • v3 Update /v3 for services endpoints details
  • v3 Validate request to update service instance name details
  • v3 Validate request to update service instance plan details
  • v3 Validate space/org quotas on plan update details
  • v3: Update managed service instance using SYNC broker details
  • Add available buildpacks to CF-for-k8s Store & Custom Builder details
  • Create ADR for refactoring KubeClients/ CRD interactions details
  • Create script to mass-produce resources in CC details
  • Detect process_types from kpack-built image metadata details
  • Emit app events in a way that is consumable by cf-for-k8s logging details
  • Make "cloud_controller_ng", " cc_uploader", " cloud_controller_worker", " cc_deploymenet_updater" ," tps" , " cloud_controller_clock" and " blobstore'' jobs logs human readable based on property details
  • Remove snyk details
  • Service plan must allow include of service offering/space.organization details
  • Unable to disable Route Services details
  • Updating a service broker results in two offerings with the same name details
  • fix bridge unit tests details

Cloud Controller Database Migrations

None

Pull Requests and Issues

  • cloudfoundry/cli #1940: v7: set-org-role should not always default --origin to uaa details
  • cloudfoundry/cloud_controller_ng #1567: [Feature Request]: Status in Revisions details
  • cloudfoundry/cloud_controller_ng #1609: Add ADR for refactoring k8s clients details
  • cloudfoundry/cloud_controller_ng #1625: Unusable Buildpacks If Upload Fails details
  • cloudfoundry/cloud_controller_ng #1683: Creating a deployment that violates a quota results in 500 unknown error details
Assets 3
Loading