v2.3.0

Revert "WIP - bosh create-env implemented for gcp"

This reverts commit 4c8ab23461fe727720e53726c5a90789233e8f2b.

v2.1.1

Add default network and vm_type to cloud config

[#136470885]

Signed-off-by: Angela Chin <[email protected]>

v2.1.0

• bbl create-lbs no longer prints the cert and key
• A websockets loadbalancer has been created. cf logs should work on cloudfoundry installed to BBL Foam.
• A DNS entry will be created if you supply --domain
• A custom name can be supplied to bbl up to override the Lake name that was previously randomly generated.
• bbl delete-lbs works as expected on GCP
• bbl update-lbs works as expected on GCP

v2.0.9

Merge branch 'master' into develop

v2.0.8

Adds a load balancer for TCP routing. bbl create-lbs --type cf to add this to an existing deployment.

v2.0.7

Manually fix SHA1 of bosh release

v2.0.6

Fix SHA1 for pre-compiled bosh release.

v2.0.5

• Rename router and ssh-lb to match CF deployment
• Add support for SSH to lb creation

v2.0.4

Add alias to cf-internet-not-required to remove lockstep upgrade with…

v2.0.3

This release finishes initial support for Google Cloud Platform. It should be feature complete for deploying concourse and cf-deployment for many teams.

As a result of the new IaaS there is a single, breaking, change for users on AWS. When running bbl up on a completely new environment you must supply --iaas aws. If you have an existing bbl-state.json, the flag is not required. Please be aware of this if you upgrade beyond 1.x and have been using bbl up in your continuous integration.

Missing functionality:

• bbl create-lbs --type cf does not support ssh or TCP routing, yet
• update-lbs is not yet implemented for GCP users. Workaround: delete-lbs and create-lbs
• lbs to list lbs is not yet present for GCP users. Workaround: use the GCP console to discover the lb IP address.