Skip to content


You can find the source of this version on GitHub at cloudfoundry/bosh. It was created based on the commit 3434c3d5.

Release Notes

Reported problems: - Earlier versions of the Director erroneously applied instance group properties to addons. Addons only should see properties specified in runtime config. This v258 no longer exhibits old behaviour. - HM started to query /deployments/:name/instances API which sometimes causes high CPU usage in the Director since it performs large number of queries - One workaround until this problem is fixed is to re-run bosh deploy on your existing deployments

New Features: - Added --dry-run flag to bosh deploy that exits right before starting an actual deploy - Useful to validate that deployment manifest, releases, and stemcells are all correct - Added ability to tag VMs with arbitrary tags within a deployment via top level tags key - [beta] Support multiple persistent disks for each instance within an instance group - Persistent disks are considered unmanaged by the Agent so release jobs have to partition and format them - Added experimental --fix flag to bosh deploy to automatically recreate VMs that are not responsive - Added spec.ip for ERB templates for jobs to get their own IP - Operator can set networks to be addressable via default key to change which IP jobs see - Add support for OS-specific addons - Director allows to specify where addons are included based on deployment, OS and instance group names

Improvements: - Write Director events to syslog in addition to recording them into DB - Works great with cloudfoundry/syslog-release - Send and env.bosh.groups to CPIs for automatic tagging, etc. - Used primarily for automatic creation of Azure availability sets and GCP security groups - Switched to using davcli in the Director to make blobstore access consistent with the Agents - Fixed HM Resurrector to bring back VMs that were successfully deleted but failed to be recreated - Switched HM to use /deployments/:name/instances endpoint - Avoid env.bosh.remove_dev_tools flag causing VM recreate - Allow Director to handle badly encoded UTF-8 data in CPI responses - Support percentages in canaries and max in flight update configurations - Fix addon properties handling when single addon references multiple jobs - bosh cck no longer shows empty VM cids in problem it reports - Avoid stopping / taking snapshots of stopped instances - Task can be cancelled when Director is waiting for the VM to be in specific state - Switched showing release version in bosh status

Version bumps: - Bump s3cli in the Director to latest - Adds support for server side encryption for S3 - GCS support

Misc: - Continued working on config server support - Continued working on bosh CLI v2 integration test suite


You can reference this release in your deployment manifest from the releases section:

- name: "bosh"
  version: "258"
  url: ""
  sha1: "66f7ce02eda71d63fc13e86a6d49fa5a8398c906"

Or upload it to your director with the upload-release command:

bosh upload-release --sha1 66f7ce02eda71d63fc13e86a6d49fa5a8398c906 \