github cloudfoundry/capi-release 1.12.0
CAPI 1.12.0

latest releases: 1.134.0, 1.133.0, 1.132.0...
7 years ago

CC API Version: 2.66.0 and 3.1.0

Service Broker API Version: 2.11

CAPI Release

  • As a CF Security Auditor, I would like components to receive sensitive configuration via config file for tps details
  • As a CF Security Auditor, I would like components to receive sensitive configuration via config file for nsync details
  • As a CF Security Auditor, I would like components to receive sensitive configuration via config file for stager details

Cloud Controller

  • CAPI should support HTTP health check for applications details
  • As an Auditor, I would like to discover when a user is added or removed from an Organization via audit events details
  • As an Auditor, I would like to discover when a user is added or removed from an Space via audit events details
  • As a Space User, I should be able to Associate Staging Security Group with the Space details
  • As an API User, Security Groups should always show a url for staging spaces details
  • NSYNC: As an Operator, I would like to be able to cancel V3 tasks without the nsync-listener running details
  • As an app developer, I expect CC not to allow setting an environment variable with an empty name so that my app does not fail details
  • Developers can stage apps using a disabled buildpack on Diego details
  • NSYNC: As an Operator, I would like to be able to run V3 tasks without the nsync-listener running details
  • As a Rails Developer, I would like tasks to set the DATABASE_URL environment variable details
  • Isolation segments should work after bridge consumption - Staging edition details
  • As an Auditor, I would like to be able to filter audit events by space_guid or org_guid details
  • As a user, I can start an app in a space that is associated with an isolation-segment details
  • As an Operator debugging an issue with a delayed job, it would be helpful to get stack traces in logs instead of in the database record details
  • As an API user, I would like to be able to learn a username via GET /v2/users/:user-guid details
  • As a CAPI developer, I can easily generate bbs protobuf ruby files details
  • STAGER: As an Operator, I would like communication between CC and Diego to always use TLS details
  • Updating an isolation segment name should be restricted. Just like assigning IS to spaces or Org Defaults details
  • An org with apps in spaces without assigned ISes cannot have its default IS changed details

Pull Requests and Issues

Stager

Job Spec Changes

  • Removed properties.capi.stager.docker_registry_address

Don't miss a new capi-release release

NewReleases is sending notifications on new releases.