Releases: cloudfoundry/capi-release
Releases · cloudfoundry/capi-release
CAPI 1.39.0
Please do not use this release. It contains a migration that can take very long to execute.
CAPI 1.38.0
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
nolink 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
CAPI 1.37.0
Please do not use this release. It contains a migration that can take very long to execute.
CAPI 1.36.0
Highlights
- Operators should begin deploying without the legacy Cloud Controller Bridge translation components. This document provides additional information.
- Introduce support for multiple buildpacks.
- Resolve issue where TASK_STOPPED usage events were not recorded for an app that was deleted with in-flight tasks.
CC API Version: 2.90.0 and 3.25.0
Service Broker API Version: 2.12
CAPI Release
Cloud Controller
- API client can request an app or build with lifecycle including multiple buildpacks details
- API client can successfully stage a droplet with multiple buildpacks details
- API client can cancel a task using POST with a /actions url details
- API client can observe failure reason for a job details
- API client can scale a process using POST with a /actions url details
- API client can start an app using POST with a /actions url details
- API client can stop an app using POST with a /actions url details
- API client does NOT see stage link details
- API client sees TASK_STOPPED app_usage_event when the parent app is deleted and the task is still running details
- Can't update environment variables with v3 api when app has no existing environment variables details
- Loggregator can check log access using mtls details
- ProcessSyncer should not fail to update freshness when attempting to update a LRP that no longer exists (race condition) details
- Stopping our clock job should not timeout details
Pull Requests and Issues
- cloudfoundry/capi-release #48: /v2/spaces/<SPACE_GUID>/security_groups returns duplicate entries details
- cloudfoundry/cloud_controller_ng #843: Error when using long Docker Registry passwords details
- cloudfoundry/cloud_controller_ng #848: Missing indexes for some SELECT queries, which are frequently executed by CC details
CAPI 1.35.0
Highlights
- Use golang 1.8
CC API Version: 2.89.0 and 3.24.0
Service Broker API Version: 2.12
CAPI Release
- PM can confirm that capi-release components are using golang 1.8 details
Cloud Controller
CAPI 1.34.0
Please do not use this release.
CAPI 1.33.0
Please do not use this release.
CAPI 1.32.0
Highlights
- Introduces metrics for staging and and app syncing when performed by the CC instead of the CC Bridge
CC API Version: 2.86.0 and 3.21.0
Service Broker API Version: 2.12
CAPI Release
Cloud Controller
- API Client can delete a package asynchronously details
- Do not pass in timeout for LRP health check definitions details
- Operator can observe metrics for number of invalid lrps being requested details
- Operator can observe metrics for staging requests details
- Operator can observe sync duration metric details
- Verify issuer when validating oauth token details
Pull Requests and Issues
- cloudfoundry/cloud_controller_ng #834: Service broker create instance schemas details
CAPI 1.31.0
Important
- The way that resources are stored for resource matching has changed. Resource files are now stored in a subdirectory, named
app_bits_cache, in the resource bucket . This means existing resource files will be orphaned. This change is in preparation for automated orphan cleanup for Cloud Controller managed blobstores. If storage space is a concern for a given environment, then operators should consider manually purging the resource bucket after this release is deployed. Before purging the resource bucket, please ensure that resources are stored in a different bucket than all other resources (droplets, packages, buildpacks).
Highlights
- Introduces support for Service Broker API 2.12
- Resolves several issues when syncing LRPs and Tasks with Diego
CC API Version: 2.85.0 and 3.20.0
Service Broker API Version: 2.12
CAPI Release
Cloud Controller
- API Client can delete an app asynchronously details
- API Client experiences improved performance of
GET /v3/app/<guid>/tasksdetails - API client can discover how to allow all types and codes for ICMP security group rules. details
- API client can discover link for
/v3/processesdetails - API client can discover the logging api location details
- API client should NOT receive error when canceling a task diego does not know about details
- API client should follow a consistent schema to specify an service-binding-to-app relationship when creating a service binding details
- API client should not be able to specify custom buildpacks for an app when platform has disabled custom buildpacks details
- API client should not be able to use custom buildpacks when the platform has disabled custom buildpacks details
- API client should see that next_url does NOT omit the organization_guid filter for /v2/routes details
- App developer should be able to specify HTTP Healthcheck for processes using the v3 api details
- CC Sync job fails when app has shared domain with
router_group_guiddetails - Do not fail sync when there is a race condition creating LRPs details
- With many processes, if the first one fails due to invalid LRP, freshness will still be bumped even if there is another error details
Pull Requests and Issues
- cloudfoundry/cli #1096:
cf pushfails when file mode is invalid, but doesn't say which file was the cause details - cloudfoundry/cloud_controller_ng #821: When calling /v2/spaces/:spaceGuid/services, space-scoped services return an empty array for their service plans details
- cloudfoundry/cloud_controller_ng #831: Misleading documentation for Resource Match API ? details
- cloudfoundry/cloud_controller_ng #835: Support Open Service Broker API v2.12 details
CAPI 1.30.0
Important
- This release includes large, internal changes for handling staging. As a result, some staging tasks may fail during deployment when the cloud controller jobs are updating.
- DEA is no longer supported as a backend runtime.
Highlights
- Introduce a
readpermission for service brokers to query when displaying dashboards for service instances. Read here for more. - Fixes some issues regarding tasks erroneously failing or being stuck in a
RUNNINGstate. - Introduce Builds resource in the V3 API to represent the staging process.
CC API Version: 2.84.0 and 3.19.0
Service Broker API Version: 2.11
CAPI Release
Cloud Controller
- API client can discover the network-policy api location details
- API client can observe STAGING_START and STAGING_STOP usage events based on builds details
- API client can see that LANG environment variable is set for tasks details
- API client should NOT receive errors when creating/deleting buildpacks concurrently details
- API client should NOT see any fields related to builds on droplet details
- API client should create droplet by POST /v3/builds instead of POST /v3/packages/:guid/droplets details
- API client should see fields nested under result move to the top level on droplet details
- API client should see that builds that do not finish staging are eventually marked failed details
- As a platform, I can send a context parameter to brokers when creating a service instance details
- Bit service can update package status and checksums details
- Bump nokogiri to >= 1.7.2 details
- CF users should need
cloud_controller.readscope rather thancloud_controller.writeto view isolation segment for org an space details - Cloud Controller double-counts memory (and disk?) against quota when updating a task details
- Operator should observe that an interrupted sync job does not result in waiting 4 hours until bulking continues details
- Sync job should continue to update LRPs, tasks, and bump freshness even if a LRP Update returns a
Error_InvalidRequestdetails - API Client should NOT see 500 error when GET /v2/organizations/:guid/users has an error communicating with UAA details
- API client can discover from a build the user that created the resource details
- API client can observe build create and droplet create audit events at the correct points in the staging lifecycle details
- investigate route deduping issue for buildpack vs docker with legacy bridge details