Updated to UAA Release 3.16.0
In this release, we introduce support for bosh linked
The uaa job can now consumes a bosh linked
database resource as an alternative to the manifest property
uaadb.address. This is a backwards-compatible change. If your deployment manifest includes the
uaadb.address property it will take precedence over any bosh links that may be available.
Similarly, a bosh linked
router resource can be used in place of
uaa.proxy.servers. Values specified in the manifest for
uaa.proxy.servers will continue to take precedence over a bosh link router resource.
Upload this release version to the Director:
$ bosh upload-release https://bosh.io/d/github.com/cloudfoundry/uaa-release?v=34 --sha1 dcb2a2911c1592b2c582237e801fb5d0c7639674
Modify deployment manifest to use this release in addition to any other used releases:
releases: - name: uaa version: "34"
Finally add needed deployment jobs and specify values for required properties.
Optionally download sha1: dcb2a2911c1592b2c582237e801fb5d0c7639674 release tarball locally:
# ...or download it directly using curl $ curl -L -J -O https://bosh.io/d/github.com/cloudfoundry/uaa-release?v=34 # or with wget... $ wget --content-disposition https://bosh.io/d/github.com/cloudfoundry/uaa-release?v=34