v6.1.0

• We have fixed an issue with our Azure integration with cf-deployment. Azure users should now be able to deploy cf-deployment and have working endpoints with no manual adjustment of the load balancers
• We have corrected the credhub credentials (CREDHUB_CLIENT, CREDHUB_SECRET) to match changes in bosh-deployment
• We have consistently added bosh.example.com in every IaaS when you have set a domain name.
• We introduced a new bbl subcommand bbl cleanup-leftovers --filter bbl-env-ontario for unceremoniously and forcibly wiping IaaS accounts or BBL environments that are half cleaned up, or have deployed non-bbl VMs. Thanks to @genevieve's leftovers which we rely on to provide this functionality.
• It is now possible to bbl down even if no IaaS resources have been created. Previously bbl plan && bbl down would fail.
• Current jumpbox-deployment: cloudfoundry/jumpbox-deployment@edbf809
• Current bosh-deployment: cloudfoundry/bosh-deployment@14ef8a2
• Linux sha256: cefc3a6e5f61fc9694b048ba7552ab89d3ccca8e877acb894e3cdc36bbcccb02
• OSX sha256: c3562e5be92583e2d4e23a3a3a7656acad4a74eedd9e7773b41c4a35ae80eea9- Windows sha256: 054c1af49aa6434c26f8655b433be6956bb65d51055486b2a66fa3dbdba88307
  Known Issues: Windows support is incomplete.