All releases of the BOSH CPI for Google Cloud Platform will be documented in this file. This project adheres to Semantic Versioning.
25.5.0 - 2016-10-17
- Release uses Go 1.7.1
- A backend service previously could not have multiple instance groups with the same name. This release fixes that, and you may have instance groups with the same name associated to a backend service.
25.4.1 - 2016-09-14
- Tags that are applied by the director on VM create will be truncated to ensure they do not violate the 63-char max limit imposed by GCE.
25.4.0 - 2016-09-14
- When using a custom service account, a default
cloud-platform
scope is used if no custom scopes are specified.
25.3.0 - 2016-09-02
- S3 is now a supported blobstore type.
25.2.1 - 2016-08-18
- Underscores are replaced with hyphens in metadata that is applied as labels to a VM.
- Complete Concourse installation instructions, including cloud config and Terraform.
25.2.0 - 2016-08-18
- Any metadata provided by bosh in the
set_vm_metadata
action will also be propagated to the VM as labels, allowing sorting and filter in the web console based on job, deployment, etc.
25.1.0 - 2016-08-18
- The
service_account
cloud-config property may now use the e-mail address of a custom service account.
25.0.0 - 2016-07-25
- The
default_zone
config property (in thegoogle
section of a manifest) is no longer supported. Thezone
property must be explicitly set in thecloud_properties
section ofresource_pools
(orazs
for a cloud-config director.)
24.4.0 - 2016-07-25
- An explicit region is used to locate a subnet, allowing subnets with the same name to be differentiated.
24.3.0 - 2016-07-25
- A
resource_pool
's manifest can now specifyephemeral_external_ip
andip_forwarding
properties, overriding those same properties in a manifest'snetworks
section.
24.2.0 - 2016-07-25
- This changelog
- 3262.4 stemcell
- All tests now use light stemcells
24.1.0 - 2016-07-25
- Instance tags can be specified in any
cloud_properties
section of a BOSH manifest
- The dummy BOSH release is no longer part of the CI pipeline
- Integration tests will use the CI pipeline stemcell rather than requiring an existing stemcell in a project