<The way this document looks in the raw is intentional. For a discussion of the intention, Please see https://github.com/JesseTAlford/texts/blob/master/the-art-of-markdown.md>

This repo contains concourse tasks for use with cf-deployment. If you are trying to deploy to GCP, you may wish to check the GCP Deployment Guide. Each task is in its own directory. A task will generally be composed of a task.yml to be referenced in pipelines, a supporting task file, and a Dockerfile. The Dockerfile is built and pushed to Dockerhub regularly in CI maintained by the CF Release Integration team here.

It should be clear how to use each task from the task.yml and the description below. If you find that it is not, please contact the Release Integration team in our Slack channel dedicated to supporting users of cf-deployment. Alternatively, you can open an issue.

Tasks are listed here alphabetically, along with a brief description meant to be used alongside the task.yml within each task directory to understand the tasks' purpose, interface, and options. Each title is also a link to the appropriate task.yml.

This destroys the director and infrastructure created by bbl. Debug output is written to bbl_destroy.txt to help debug failures in this task.

This uses bbl to create your infrastructure and deploy a BOSH director. Debug output is written to bbl_up.txt, bbl_create_lbs.txt, and bbl_update_lbs.txt to help debug failures in this task. This task requires a certificate and key which can be generated using the commands specified here.

This performs a BOSH deployment and outputs a vars-store. Optionally, operations files may be applied to the deployment manifest.

It's also configurable to regenerate the vars-store on each deployment though this is not the default behavior. This is helpful for testing changes to variable generation, but is only expected to work with fresh deployments.

This creates and applies an additional operations file to cf-deployment.yml, which causes BOSH to create, upload, and use a dev release from the provided release folder in place of the version specified in cf-deployment.yml. This is useful for testing an upstream component. Otherwise identical to the bosh-deploy task above.

This uploads the stemcell version specified in cf-deployment to the BOSH director.

This will toggle the specified feature-flags based on their boolean values.

This updates integration files to be consumed by CATs and RATs with credentials drawn from a vars-store.