Skip to content

v5.0
Compare
Choose a tag to compare
@dsabeti dsabeti released this 29 Dec 19:01
v5.0
292304f
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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.
Assets 2
Loading