Highlights
- Fixed bug that prevented apps with long character count env variable from starting up properly
CC API Version: 2.146.0 and 3.81.0
Service Broker API Version: 2.15
CAPI Release
Cloud Controller
- API client remove a space quota from a space details
- API client author can see information in the upgrade guide about how to use quotas on v3 details
- API client can apply a quota to spaces details
- API client can create a space quota details
- API client can delete a space quota details
- API client can delete an organization quota details
- API client can enable/disable SSHing for a space using v3 details
- API client can filter space quotas details
- API client can list features for a space using v3 details
- API client can list space quotas details
- API client can update organization quotas details
- API client can update space quotas details
- API client can view if SSHing is enabled for a space using v3 details
- API organization_quota presenter should list relationships directly before links details
- Apply permissions to GET list of service plans details
- As a /v3 API user, I want the correct permissions model to be applied for my interactions with the service plan GET endpoint details
- As a /v3 API user, I want to GET a list of service offerings filtered by org GUID details
- As a /v3 API user, I want to GET a list of service offerings filtered by space GUID details
- As a /v3 API user, I want to GET a list of service plans filtered by Broker Catalog IDs details
- As a /v3 API user, I want to GET a list of service plans filtered by Names details
- As a /v3 API user, I want to GET a list of service plans filtered by Service Broker GUIDs details
- As a /v3 API user, I want to GET a list of service plans filtered by Service Broker Names details
- As a /v3 API user, I want to GET a list of service plans filtered by Service Instances GUIDs details
- As a /v3 API user, I want to GET a list of service plans filtered by Service Offering GUIDs details
- As a /v3 API user, I want to GET a list of service plans filtered by Service Offering Names details
- As a /v3 API user, I want to GET a list of service plans filtered by available plans details
- As a /v3 API user, I want to GET a list of service plans filtered by organization_guids details
- As a /v3 API user, I want to GET a list of service plans filtered by space_guids details
- As a /v3 API user, I want to GET service plans with links and relationships details
- As a /v3 API user, I would like to manage metadata for a service plan details
- As a /v3 user I want to see maintenance_info when I query /v3/service_plans and /v3/service_plans/:guid details
- As a v3 API admin user, I want to delete a service plan details
- As a v3 API space developer user, I want to delete a service plan of a space scoped broker details
- As a v3 API user, I want to delete service offerings and all the corresponding plans and instances (with purge) details
- As an operator, when a service plan is deleted via the v3 API, I would like to see an audit event logged details
- Create droplet after build succeeds in kpack details
- Deployments documentation does not reference status details details
- Document GET a single service plan using a GUID details
- Duplicate service offerings makes CLI CI fail details
- Ensure API responses are in the correct order details
- Fix
contain_metadatamatcher details - Get Plan Visibility details
- Lifecycle tests for service broker details
- Org & Space Quotas are not experimental in the API docs and v3 link details
- Run a droplet that was built with kpack on k8s details
- Set Plan Visibility: organization details
- Set Plan Visibility: public / admin details
- Space Features are not experimental in the API docs details
- Update service plan response object details
- Using a space quota with unlimited memory results in a "memory exceeded" error details
- add tests and fix endpoints for deleting with metadata details
- capi-k8s-release can be configured to use local dev OCI images OR publicly available defaults details
- when updating v3/build state, developers in other spaces shouldn't be able to trigger 403s details