cloudfoundry/capi-release 1.26.0

CAPI 1.26.0

on GitHub

Highlights

• Resolved issue with /v2/events next_url containing an invalid next page

CC API Version: 2.80.0 and 3.15.0

Service Broker API Version: 2.11

Job Spec Changes

cc_uploader

• Required properties to enable diego to use mutual_tls for uploading assets to cloud controller. This ca cert should match the ca cert configured for the rep in the diego deployment. See this doc for help generating certs.

  • capi.cc_uploader.mutual_tls.ca_cert
  • capi.cc_uploader.mutual_tls.server_cert
  • capi.cc_uploader.mutual_tls.server_key

• Removed properties. These properties contained an IP address and port. The ip and port values have been moved into separate fields.

  • capi.cc_uploader.listen_addr
  • capi.cc_uploader.debug_listen_addr

• New properties

  • internal_hostname
  • http_port
  • https_port
  • bind_addr
  • debug_bind_addr

CAPI Release

• Operator can enable mtls droplet upload from diego to cc-uploader details

Cloud Controller

• Operator can enable mtls droplet upload from diego to cc-uploader details
• API client can set App environment variables on a sub resource of a created app details
• Get /v2/service_plan/:guid results in a 500 UnknownError if user has a user provided service instance details
• CAPI release 1.25.0 erroneously reports the routing API as disabled when deleting shared domains details
• API client should NOT fail to stage due to missing buildpack blobs if CC thinks the buildpack exists. details
• API client should see state field instead of desired_state field on apps details

CC Uploader

• Operator can enable mtls droplet upload from diego to cc-uploader details

Pull Requests and Issues

• cloudfoundry/cloud_controller_ng #803: Events API next_url value does not work details