Skip to content


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

Release Notes

New Features: - Prepared Director to accept releases that use SHA2 for checksumming - CLI v2 is able to generate such releases with --sha2 flag - Expose instance IPs in GET /deployments/:name/{instances|vms} API endpoint when format=full is not specified - Added JSON HM plugin for supporting external HM plugins - Added --with-changed flag to run errand command so that errand does not run if its configuration was not changed - Add deployment teams to Datadog HM plugin events & metrics - Emit teams from Director /deployments API endpoint - Emit teams information in heartbeats from HM - Expose AZ information for each instance/VM in GET /deployments/:name/instances - Record HM alerts as BOSH events - Includes process restarts, monit alerts, etc. - Batch emitted Datadog metrics via their batching API - Expose additional event filtering query params - Filtering flags are available in CLI v2 - Remove syslog_event_forwarder_enabled property in favor of using syslog-release - Track optional context ID for particular API endpoints - Provide Director-supplied request ID to CPI calls - Add generic POST /events API to allow custom event recording - Used by the HM when submitting HM alerts - Add basic multi CPI support (currently supports CPIs of the same type) - Collect logs from multiple instances if multiple instances are specified via bosh logs command (v2)

Fixes: - Filter detached instances during scan_and_fix - Resurrector will not try to resurrect detached instances anymore - Updated Director nginx server to enforce TLS 1.2 - Recreate command does not start instances that were stopped - Fixed bug where resurrected VMs would not have certain VM extensions present - Only occurs if both VM extension and VM type specify cloud property with the same key - Errands should resolve job configuration at deploy time not during run errand command - bosh delete-vm command correctly removes VM CID when vm is not found in the IaaS - Make bosh follow 301 redirects when downloading remote releases

Misc: - Continued config server API work - Continued DNS work


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

- name: "bosh"
  version: "261"
  url: ""
  sha1: "b7855edc33ece92e9e8e1b5d03c5e2c897d426d8"

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

bosh upload-release --sha1 b7855edc33ece92e9e8e1b5d03c5e2c897d426d8 \