cloudfoundry/capi-release 1.87.0

CAPI 1.87.0

on GitHub

Highlights

• Added support for metadata when creating routes
• Made log-cache endpoint more discoverable
• Added ability to add sidecars to revisions
• Added support for buildpack configured sidecars

CC API Version: 2.142.0 and 3.77.0

Service Broker API Version: 2.15

CAPI Release

[Cloud Controller]

• API User should be able to use the default-route key in the manifest details
• API client add, modify, and remove metadata on a user details
• API client can delete a user details
• API client can discover audit events on the v3 API details
• API client can discover environment variable groups on the v3 API details
• API client can discover roles on the v3 API details
• API client can filter audit events details
• API client can filter users details
• API client can get details of an audit event details
• API client can list audit events details
• API client can query users with label_selector details
• API client can update running and staging environment variable groups details
• API client can view running and staging environment variable groups details
• API client can not pass no_route query parameter when applying a manifest details
• API client can observe the metadata section in docs examples for users details
• API space apply manifest 500's when invalid buildpacks are given details
• Add log cache endpoint discovery to CAPI details
• App dev and operator receives a helpful error message if they attempt to cf enable-ssh and ssh has been disabled on the global or space level details
• App dev should be able to use cf rename without using the v2 API details
• As a developer, when using Eirini, I expect to be able to push docker images details
• As a developer, when using Eirini, I expect to be able to push docker images in registry secured by username/password details
• As a v3 API consumer, when I try to delete a broker that has service instances, I get an informative failure message details
• As a v3 API user, my POST requests to /v3/service_brokers are asynchronous and fail or warn details
• As a v3 API user, my POST requests to /v3/service_brokers are asynchronous and successful details
• As a v3 user, when I request a job status, I want to see any warnings that may have occurred details
• As an API user, I can delete service brokers that have no instances via v3 details
• Asynchronous DELETE on /v3/service_brokers/:service_broker_guid fails details
• Asynchronous DELETE on /v3/service_brokers/:service_broker_guid is successful details
• Audit events are not experimental in the API docs and v3 link details
• Buildpack configured sidecars - defining origin details
• Capture build-complete event for CAPI telemetry details
• Make sidecars work with revisions - Add details
• Mark resource matches as deprecated in the v2 API docs with a link to the new, glorious v3 resources details
• Refactor /v3/service_brokers... to use shared examples test pattern details
• Resource Matches are not experimental in the API docs and v3 link details
• Setup CI job to run stepper: true annotated tests in CI separately in parallel to cc_units details
• [V3 API] Rename "credentials" to "authentication" in the service brokers resource details
• origin: buildpack sidecars details

Cloud Controller Database Migrations

None

Pull Requests and Issues

• API Droplet upload should accept a .tar.gz file details
• API User should not get a 500 when patching destinations where an existing one is upgraded to having weights details
• Clicking on the "Resources" header in the v3 API docs goes to the incorrect section details
• Extract proper helper for race condition testing details
• Fix deadlock on parallel broker creation details
• Global feature flag to disable resource matching details
• cloudfoundry/cli #1745: not enough informations for service binding request failures details
• cloudfoundry/cloud_controller_ng #1407: Access service usage events as global auditor details
• cloudfoundry/cloud_controller_ng #1410: ports field no longer experimental details
• cloudfoundry/cloud_controller_ng #1416: Bind failure during push shows service name details
• cloudfoundry/cloud_controller_ng #1417: Add docker support in Eirini details
• cloudfoundry/cloud_controller_ng #1421: Default new_memory to 0 in sidecar validator details
• cloudfoundry/cloud_controller_ng #1423: Upgrade fog-aliyun to 0.3.5 details
• cloudfoundry/cloud_controller_ng #1427: V3 service broker delete 166631760 details
• cloudfoundry/cloud_controller_ng #1429: Fetching usage events after_guid when that guid has been pruned details
• cloudfoundry/cloud_controller_ng #1431: Change include paths to match relationship names details
• cloudfoundry/cloud_controller_ng #1432: Getting a 500 when assigning a new droplet after some deployment madness details
• cloudfoundry/cloud_controller_ng #1435: Add log-cache endpoint to / details
• cloudfoundry/cloud_controller_ng #1436: Inefficient SQL query is causing API latency up to 60 sec details
• cloudfoundry/cloud_controller_ng #1438: Delete a broker with SIs will fail with a helpful message details
• cloudfoundry/cloud_controller_ng #1439: Add app sub-resource relationships details
• cloudfoundry/cloud_controller_ng #1440: As a v3 API user, my POST requests to /v3/service_brokers are asynchronous details
• cloudfoundry/cloud_controller_ng #1445: v3-apply-manifest fails with unknown error when mapping apps.internal route details
• cloudfoundry/cloud_controller_ng #1446: SpaceListFetcher.fetch_all fails when organization_guids and label_selector are both specified details
• cloudfoundry/cloud_controller_ng #1447: Use a nested query to allow searching spaces with orgs & labels details
• cloudfoundry/cloud_controller_ng #1458: Revert "Revert "Add docker support in Eirini"" details
• cloudfoundry/cloud_controller_ng #1461: Rename 'credentials' to 'authentication' when creating a service broker details
• cloudfoundry/cloud_controller_ng #1464: V3 async delete broker 168511247 details
• cloudfoundry/routing-release #152: Clarify on the usage of multiple app ports details
• fixup package listing to use joins details
• Mark audit events as deprecated in the v2 API docs with a link to the new, glorious v3 resource details