github cloudfoundry/capi-release 1.93.0
CAPI 1.93.0

latest releases: 1.134.0, 1.133.0, 1.132.0...
pre-release4 years ago

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

Highlights

  • Docker ports are now respected for Eirini workloads

CC API Version: 2.148.0 and 3.83.0

Service Broker API Version: 2.15

CAPI Release

  • create a way for non-http-server jobs to have their readiness checked details

Cloud Controller

  • API client author can see information in the upgrade guide about differences between your starting an app in v2 vs v3 details
  • API client author can see information in the upgrade guide about how to use security groups on v3 details
  • API client author can see information in the upgrade guide about the absence of a "restage" endpoint in v3 details
  • API client can bind an existing security group to a space (running) details
  • API client can bind an existing security group to a space (staging) details
  • API client can delete security groups details
  • API client can unbind an existing security group from a space (running) details
  • API client can unbind an existing security group from a space (staging) details
  • API client can update security groups details
  • API client can list all running security groups that are applied to apps in a space details
  • API client can list all staging security groups that are applied to apps in a space details
  • API client can see a link to the apply manifest endpoint on a space resource details
  • API client can specify a schema version when applying a space manifest details
  • CLI user should get a meaningful error if they run cf start and I do not have an uploaded package details
  • Space Manifests are not experimental in the API docs and v3 link details
  • v3 Add documentation url in the offering top level properties details
  • v3 Filter SI by plan guid and name details
  • v3 Filter SI by type (managed or user-provided) details
  • v3 Get details of service plan in service instance request details
  • v3 Get details of space in service instance request details
  • v3 Include service offering in service plan offering details
  • v3 List SI "fields" should be added individually details
  • v3: Create MSI fails - Orphan mitigation details
  • v3: Get service instance parameters (retrieve from broker) details
  • v3: Get service instance parameters details
  • v3: Respect "Retry-After" header when polling Last Operation details
  • v3: Respect service_instance_creation feature flag when creating a service instance details
  • v3: audit events and logging when creating SIs details
  • v3: Create a user provided service instance details
  • v3: Create managed service instance using ASYNC broker details
  • v3: Create managed service instance using SYNC broker details
  • v3: Handling last operation responses on create managed service instance details
  • v3: cannot create service on suspended orgs details
  • Add missing request spec shared example details
  • Add support for buildpack caching details
  • As a developer, when pushing a Docker image with OPI Staging, I expect to be able to configure the listening port details
  • As a v3 API user I want to get a single service instance details
  • As a v3 API user, I want to GET a list of all MSI and UPSI (without relationships or links) details
  • As a v3 API user, I want to GET a list of all SIs including links and relationships details
  • As a v3 API user, I want to be able to get space and organization as an included fields resource when getting a single service instance details
  • As a v3 API user, I want to be able to get spaces and organisations as an included fields resource when getting all SIs details
  • As a v3 API user, I want to be able to get the service plan and offering and broker as an included field resource when getting all SIs details
  • Authorised user can get credentials for UPSI details
  • Environment variable group validation should not show Ruby hash syntax details
  • Exploratory testing for service offerings resource details
  • Exploratory testing for service plans resource details
  • create a way for non-http-server jobs to have their readiness checked details
  • in capi-release's jobs, confirm that readiness endpoints are use for all healthchecks and lifecycle hooks details

Cloud Controller Database Migrations

None

Pull Requests and Issues

  • cloudfoundry/cloud_controller_ng #1573: Upgrade fog-aliyun to 0.3.8 details

Don't miss a new capi-release release

NewReleases is sending notifications on new releases.