Skip to content

@capi-bot capi-bot released this Feb 14, 2019

Highlights

  • Added support for query labels in build and buildpacks V3 resources
  • CAPI now returns a 503 error with the message "API down for maintenance" during a BBR backup
  • Audit events are now captured when a revision and rollback are created
  • Deployment resource now contains a reference to the revision that was deployed
  • App resource now contains a reference to the all app revisions and deployed revisions

CC API Version: 2.132.0 and 3.67.0

Service Broker API Version: 2.14

CAPI Release

  • cloudfoundry/capi-release #121: CC clock fails to sync app processes, fails with vague certificate verification error details
  • cloudfoundry/capi-release #124: Request a new capi release to include the latest aliyun fog library details

Cloud Controller

  • API client can apply a manifest to multiple existing apps in a space details
  • API client can apply a manifest to a space and see that missing apps are created details
  • API client can apply a manifest to a space and see that missing docker apps are created details
  • API client sees error when applying a space manifest with no app names details
  • API client should be able to discover feature flags on the v3 API details
  • API client should see an error when applying a manifest with a docker key to an app with a buildpack lifecycle details
  • API client should see an error when applying a manifest with both a docker key and buildpack key details
  • Explore create-buildpack API design by/with collaborating with the Bits Service and CAPI teams to discover a way for CC to handle bits service in all three (disabled + proxy + direct) modes details
  • API client can query build with label_selector details
  • API client can query buildpack with label_selector details
  • API client can see that API requests fail due to being locked for BBR operations [503 while locked] details
  • API lists deployed revisions for an app details
  • App dev should be able to use the -t flag and server side manifests details
  • App resource contains link to app revisions details
  • As a developer, I can see the type of all service instances when fetching a space summary details
  • Audit event for rollbacks / revision details
  • CLI user can use a new --rename flag with cf update-buildpack to rename their buildpacks details
  • Deployment contains a reference to a revision that was deployed details
  • Make blobstore benchmark utility easier to run details
  • Rollback to previous revision env variables details
  • Update GET a revision endpoint to /v3/revisions/:guid details
  • Update PATCH a revision endpoint to /v3/revisions/:guid details
  • translate old cf-release "how to fix accidental pushes to master" document to make sense for capi-release details

Cloud Controller Database Migrations

None

Pull Requests and Issues

  • Scaling app via v2 api is not disabled during deployments details
  • Deployment post-start BuildpackInstaller fails with informative error messages for the StacklessAndStackfulMatchingBuildpacksExistError details
  • cloudfoundry/cloud_controller_ng #1252: Fix ./bin/console script details
Assets 3
You can’t perform that action at this time.