v5.2

• Upgrades BOSH CLI to 2.0.48
• bosh-deploy and bosh-deploy-with-created-release allow Concourse users to configure their tasks to use the BOSH Credhub instead of committing a vars-store to their env-repo:

  params:
    USE_VARS_STORE: false
  

v5.1

• Users can configure bbl-up to skip creation of load balancers by configuring SKIP_LB_CREATION: true in their parameters for the task. IS_BOSH_LITE: true also still skips load balancer creation, _regardless of the value of SKIP_LB_CREATION.
• Upgrades to bbl v5.11.5
• Upgrades to terraform 0.11.2

v5.0

cf-deployment-concourse-tasks v5.0

Breaking changes

• Upgrades (finally) to bbl 5. Please read the release notes for bbl 5 for help upgrading. Thanks to the @cloudfoundry/cf-infrastructure team for PR'ing the necessary changes to task to make this happen successfully. For users bringing up environments on AWS, make sure to read the release notes for bbl 5.10.0 carefully as well.
• bbl-up and bbl-destroy commit the entire contents of the BBL_STATE_DIR. This is a direct result of upgrading to bbl 5, whose state includes more than a single bbl-state.json file. There are a few important ramifications of this:
  1. The bbl-state input for all tasks has been renamed to env-repo.
  2. The BBL_STATE_DIR param has a default of bbl-state. Taken with the previous bullet point, by default, the bbl state is saved in env-repo/bbl-state by default, and task commits the entirety of that directory. Although unrecommended, if users still want to use the top-level directory for their bbl state, they can configure BBL_STATE_DIR: ..
  3. The updated-bbl-state output has been renamed to updated-env-repo.
  4. BBL_GCP_SERVICE_ACCOUNT_KEY is now defined as relative to the top-level directory (rather than BBL_STATE_DIR as it was previously). We made this change to avoid a bootstrapping problem with bbl creating the BBL_STATE_DIR.
• set-feature-flags has a revamped interface. Instead of gatekeeping each feature-flag with its own param, the task has two params, ENABLED_FEATURE_FLAGS and DISABLED_FEATURE_FLAGS. Each one takes a space-delimited list of flags to enable/disable. Thanks @Samze and @cloudfoundry/services-api for the contribution!

Non-breaking improvements

• BBL_GCP_PROJECT_ID and BBL_GCP_ZONE are no longer required parameters for any tasks.
• bosh-upload-stemcell-from-cf-deployment allows users to specify a MANIFEST_FILE to use to discover the necessary stemcell (the value used to be hard-coded to cf-deployment.yml).This should allow users to upload stemcells from other manifests -- for example, concourse.yml.
• bosh-deploy allows for a slew of uptimer configuration:
  • Users can run syslog availability uptime tests by configuring

    MEASURE_SYSLOG_AVAILABILITY: true
    TCP_DOMAIN: ...
    AVAILABLE_PORT: ...
    

  • Users can specify failure thresholds for uptimer.

v4.21

Downgrades to Terraform v0.10.8

v4.20

DO NOT USE: We've found issues using bbl with Terraform v0.11.0.

• bbl-up task supports an improved bosh-lite workflow
  • Concourse user can set IS_BOSH_LITE: true in their pipeline configuration, and the Concourse task will refrain from building a load balancer. Thanks to @Gerg and @ljfranklin from the CAPI team for the contribution.
  • To complete the bosh-lite setup:
    1. Concourse users should configure bbl-up with the following ops-files:

    params:
      ...
      OPS_FILES: "bosh-lite.yml bosh-lite-runc.yml gcp/bosh-lite-vm-type.yml"
      IS_BOSH_LITE: true
    

    2. Upload the cloud-config from cf-deployment/iaas-support/bosh-lite/cloud-config.yml
• Terraform updated to v0.11.0

v4.18

• Terraform 0.10.8
• bosh-upload-stemcell-from-cf-deployment supports use of version: latest for stemcells.

v4.17

• New task: bosh-deploy-with-updated-release-submodule. Allows users to specify both the release and the submodule as inputs to the task, in order to leverage the versioning semantics of Concourse resources. This task is now recommended over using bosh-deploy-with-created-release with the BUMP_SUBMODULE parameter.
• bbl-up task can now be passed a certificate chain. This should be useful for operators whose load balancer certificates are signed by a root CA or some other trusted CA managed by the operator.

v4.6

• bbl- and bosh-related tasks can be configured with IaaS credentials to allow for BOSH directors with a colocated Credhub. If an environment is created via bbl up --credhub, the credentials will not be saved in the bbl-state.json file, so they must be provided as parameters to the tasks.
• Bug fix: The collect-ops-files task, if configured with a BASE_OPS_FILE_DIR, should now correctly create a directory at collected-ops-files/$BASE_OPS_FILE_DIR before attempting to copy files into it.

v4.4

• Updates terraform 0.10.1
• bbl-up task allows users to add their own flags to the bbl up command via parameter BBL_EXTRA, via contribution from the @cloudfoundry/cf-infrastructure team. Thanks!

v4.0

• Bumps to bbl 4.0. This is a breaking change for AWS environments that did not provide the --terraform flag. Follow instructions in the bbl docs for migrating.
• bbl-up task allows the Concourse user to configure the task with an ops-file. This requires a new input called ops-files; if you don't need to provide an ops-file to bbl, map the input to your env-repo and leave OPS_FILES empty.