release: / 1.12.0

Github source: 9ff3c3ca or master branch

Changes from v1.11.0 to v1.12.0

IMPORTANT: In advance of their use in the forthcoming v1.26.0 of capi-release, the manifest-generation script and templates require three new values in the property-overrides stub, property_overrides.cc_uploader.ca_cert, client_cert, and client_key, for the CC-Uploader component to use when communicating to Cloud Controller. Please consult the TLS documentation in capi-release for more information.

IMPORTANT: As of this Diego release, we consider the route-emitter job in local mode to be ready for use in production environments for HTTP route registrations. Work is also nearly complete to enable the local route-emitter to register TCP routes, but some of the BOSH properties that configure that mode will change in the next Diego release with the conclusion of story #142885525, and the manifest-generation script will extract more values from the CF manifest automatically.

Significant changes



Local Route Emitters

Local Route Emitters: TCP (Experimental)

Instance Identity Credentials (Experimental)

v2 Loggregator API Adoption (Experimental)

Manifest Generation

Test Suites and Tooling


BOSH job changes


BOSH property changes

route_emitter and route_emitter_windows

Added uaa.ca_cert: CA certificate bundle to trust when verifying the UAA server’s certificate. Added uaa.client_name: Name of the UAA client for the route-emitter to use. Defaults to tcp_emitter. Added uaa.client_secret: Secret for the route-emitter UAA client. Added uaa.port: Port on which to communicate with the UAA. Defaults to 8443 for direct internal communication. Added uaa.skip_cert_verify: Whether the route-emitter should skip verification of the UAA server’s certificate. Added uaa.url: URL at which to communicate with the UAA. Defaults to for direct internal communication.

BOSH link changes


Upload this release version to the Director:

$ bosh upload-release --sha1 6fe4073431ac2dcb7072493fae0f6c22f780e8a2

Modify deployment manifest to use this release in addition to any other used releases:

- name: diego
  version: "1.12.0"

Finally add needed deployment jobs and specify values for required properties.

Optionally download sha1: 6fe4073431ac2dcb7072493fae0f6c22f780e8a2 release tarball locally:

# ...or download it directly using curl
$ curl -L -J -O

# or with wget...
$ wget --content-disposition