cloudfoundry/capi-release 1.38.0

CAPI 1.38.0

on GitHub

Highlights

• Introduce General Availability for several V3 resources
  • Apps
  • Processes
  • Packages
  • Builds
  • Droplets
  • Organizations
  • Spaces
  • Jobs

CC API Version: 2.92.0 and 3.27.0

Service Broker API Version: 2.12

CAPI Release

Cloud Controller

• API client can observe a service binding delete audit event and determine which app and service the binding was for details
• API client can read documentation to understand how process types are determined for an app details
• API client can set environment variables without conflicting with API metadata details
• API client can use 'current' query parameter to list the current droplet for an app details
• API client can view a specific space details
• API client sees a link to the cancel action for a Task details
• API client sees that V3 App resources are GA in the documentation details
• API client sees that app object has a links to a v3 space details
• API client sees that process object has no link to a v3 space details
• API client should NOT see unknown error when creating an invalid package details
• API client should observe "errors" field in job documentation details
• API client should receive all syslog drain urls when size exceeds 1024 and CC is using MySQL details
• As a SBA I receive a single error message when registering a schema with one parameter that has an invalid type details
• As a client tooling author, I can retrieve an empty schema for update service instance for a plan details
• As a service broker author, I can register a single plan with an update service instance schema details
• As a service broker author, I cannot register a plan with a create service instance schema that contains external references details
• As a service broker author, I cannot register a plan with a create service instance schema that does not have a type object details
• As a service broker author, I cannot register a plan with a create service instance schema that is too large details
• As a service broker author, I cannot register a plan with an invalid create service instance schema details
• As a service broker author, I cannot register a plan with an update service instance schema that does not meet our schema restrictions details
• As a service broker author, I cannot register a plan with an update service instance schema without a type details
• As an SBA I receive a single error message when registering a schema that uses a meta schema details
• As an SBA I receive clearly separated error messages when registering an invalid schema details
• As an operator, I want CC to not break when UAA disables GETs to token endpoints details
• Bits service can update package state when copying without supplying checksums details
• CLI can discover CF networking API endpoints and versions details
• Cloud Controller Worker drain script references incorrect pid file. details
• V3 API Docs should list DOWN as a valid state for process stats details

Pull Requests and Issues

• cloudfoundry/cloud_controller_ng #856: Filtering Space Services by Broker causes DB error details
• cloudfoundry/cloud_controller_ng #827: Create-service-broker does not seem to actually create a service broker for openbroker details
• cloudfoundry/cloud_controller_ng #855: Missing filter for spaces/service_instances details
• cloudfoundry/cloud_controller_ng #861: Problem with CF event lifecycle details
• cloudfoundry/cloud_controller_ng #862: details field not documented in response of GET /v2/apps/:guid/instances details