v2.0.1

This release adds initial support for Google Cloud Platform. Support is not fully complete, this is a preview release for alpha testing. It should be feature complete for deploying concourse, see concourse.md for instructions on customizing a manifest to deploy concourse to a BBL GCP environment.

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.

Known issues:

• The cloud-config generated does not yet cover all of the vm_extensions used in cf-deployment

Missing functionality:

• bbl create-lbs --type cf is not yet present for GCP users
• delete-lbs is not yet present for GCP users

v1.2.1

Changes:

• State validation errors are now consistent across commands.
  Relevant stories:
  • https://www.pivotaltracker.com/story/show/130496861
  • https://www.pivotaltracker.com/story/show/133459499

v1.2.0

This release adds a few new features and fixes regressions introduced by bbl 1.1

Bumps dependencies:

• BOSH director version: 259
• Stemcell version: 3263.8
• AWS CPI version: 60

Changes:

• Adds bosh-ca-cert back for backward compatibility with bbl 1.0 details
• State migration message will now print to STDERR details
• bbl destroy is idempotent if the --skip-if-missing flag is provided details
• bbl provides more meaningful error messages due to insufficient permissions details
• bbl sets the BOSH director gateway_host property for easier bosh ssh details.
  NOTE: If you've bbl'd up with a director prior to this version, you must bbl up again in order to take advantage of this new behavior.
• bbl up optionally accepts AWS credentials as ENV vars instead of flags detail.
  The ENV flags are:
  • BBL_AWS_SECRET_ACCESS_KEY
  • BBL_AWS_ACCESS_KEY_ID
  • BBL_AWS_REGION

v1.1.0

This release is marked as a pre-release due to a couple issues that have been found with it:

1. It introduces a breaking change, renaming bbl bosh-ca-cert to bbl director-ca-cert.
2. Commands which are only supposed to output a single value (to make it easy to use in scripts or within other commands) now prints out "migrating state.json to bbl-state.json", breaking that workflow.

v1.0.0

Print the OS and Arch info in version

[#108058976]