Releases: cloudfoundry/bosh-bootloader
Releases · cloudfoundry/bosh-bootloader
v4.10.0
- Commands which do not require IaaS keys no longer require them for
--credhub
environments update-lbs
is now just an alias forcreate-lbs
. Both commands will create-or-update as necessary. As a result the--skip-if-existing
flag has been removed fromupdate-lbs
, as this is has been the behavior ofcreate-lbs
for some time. Be wary of this if you use that flag in your pipelines.- Added
bbl jumpbox-deployment-vars
to support--no-director
workflow for--credhub
environments - Current jumpbox-deployment: cloudfoundry/jumpbox-deployment@8c7c949
- Current bosh-deployment: cloudfoundry/bosh-deployment@c576a38
v4.9.2
This release only includes changes to deployment manifests.
- Current jumpbox-deployment: cloudfoundry/jumpbox-deployment@8c7c949
- Current bosh-deployment: cloudfoundry/bosh-deployment@c576a38
v4.9.1
This release only includes changes to deployment manifests.
- Current jumpbox-deployment: cloudfoundry/jumpbox-deployment@8c7c949
- Current bosh-deployment: cloudfoundry/bosh-deployment@b1bd021
v4.8.0
up
on Azure give you a director and you can deploy to that director, as long as you do not need LBs*- Better guarding against getting two environments with the same name
- Current jumpbox-deployment: cloudfoundry/jumpbox-deployment@8c7c949
- Current bosh-deployment: cloudfoundry/bosh-deployment@073a578
KNOWN ISSUES:
- *create-lbs, delete-lbs, update-lbs are not implemented on Azure
- Those using the credhub feature flag must supply IaaS credentials in more situations than normally required, the validation here is over-zealous
v4.7.3
This release only includes changes to deployment manifests.
- Current jumpbox-deployment: cloudfoundry/jumpbox-deployment@8c7c949
- Current bosh-deployment: cloudfoundry/bosh-deployment@073a578
v4.7.2
This release only includes changes to deployment manifests.
- Current jumpbox-deployment: cloudfoundry/jumpbox-deployment@8c7c949
- Current bosh-deployment: cloudfoundry/bosh-deployment@6519304
v4.7.1
This release only includes changes to deployment manifests.
- Current jumpbox-deployment: cloudfoundry/jumpbox-deployment@8c7c949
- Current bosh-deployment: cloudfoundry/bosh-deployment@c0f6ca9
v4.7.0
- Azure
bbl up
is now mostly feature complete. - GCP now allows traffic from a particular IP range that will hopefully quash 502s.
- AWS load balancer vm extensions are now consistent with GCP.
- Current jumpbox-deployment: cloudfoundry/jumpbox-deployment@8c7c949
- Current bosh-deployment: cloudfoundry/bosh-deployment@9b96e91
v4.5.1
This release only includes changes to deployment manifests.
- Current jumpbox-deployment: cloudfoundry/jumpbox-deployment@8c7c949
- Current bosh-deployment: cloudfoundry/bosh-deployment@9b96e91
v4.6.0
- Adds a helpful error message when the --domain flag is irrelevant
- Adds a GUID to statefile
- Current jumpbox-deployment: cloudfoundry/jumpbox-deployment@8c7c949
- Current bosh-deployment: cloudfoundry/bosh-deployment@7362037