Highlights
- Some Cloud Foundry deployments may have
TASK_STARTEDusage events without correspondingTASK_STOPPEDevents, even though the task is completed or the app has been deleted. The bug that caused that was fixed in capi-release 1.36.0. This release will backfill missingTASK_STOPPEDevents to allow billing to complete the task lifecycle. Because we do not know when the task completed, we will record as if it ran for one second, to prevent over billing.
CC API Version: 2.94.0 and 3.29.0
Service Broker API Version: 2.12
CAPI Release
- Bump to latest nginx in capi-release details
Cloud Controller
- API client can view a specific organization details
- API client should NOT see unknown error when restaging a V3 app details
- As a service broker author, I can register a single plan with a service binding schema details
- API client can create a space details
- API client can create an organization details
- API client can discover app ssh info from the '/' endpoint details
- API client can observe an audit event when application bits are uploaded in v2 details
- API client can order organizations by name details
- API client can order spaces by name details
- API client can view an organization link on space details
- API client does NOT see documentation for 'order-by' filter accepting 'name' filter on all List droplets endpoints details
- API client does NOT see incorrect docs for env_var_visibility feature flag details
- API client should see better error message when updating user provided service instances using the managed service instance API details
- Do a better job of improving the performance of add_missing_task_stopped_usage_events migration details
- Docker-image-based app fails to start if it exposes no ports details
- Operator observes that a CC job does not receive traffic when the CC is down. details
- Operator sees network metadata on diego task definitions details
- V2 -> V3 App model migration fails when duplicate route mappings exist details