When signed URLs are enabled, no agent user/password should be specified in Director's deployment manifest for CPIs config.
This PR relates to previous work in:
cloudfoundry/bosh#2327
cloudfoundry/bosh-deployment#423
cloudfoundry/docs-bosh#755
cloudfoundry/bosh-davcli#12
cloudfoundry/bosh-aws-cpi-release#118
cloudfoundry/bosh-google-cpi-release#327
cloudfoundry/bosh-azure-cpi-release#642
cloudfoundry/bosh-openstack-cpi-release#242
Here we make the properties blobstore.agent.{user,password} optional.
Worth to note, since cloudfoundry/bosh-agent@b4ae2397 shipped in Agent v2.42.0 on November 2017, the blobstore.options (at the root of the Agent settings JSON) are not used anymore by the Bosh Agent. So nowadays that no more supported Stemcell ships with older Agents, the CPIs should not add those properties anymore to the Agent settings.
ERB unit tests have been added to provide proper coverage for the new use-case. Then can be run with:
When signed URLs are enabled, no agent user/password should be specified in Director's deployment manifest for CPIs config.
This PR relates to previous work in:
Here we make the properties
blobstore.agent.{user,password}optional.Worth to note, since cloudfoundry/bosh-agent@b4ae2397 shipped in Agent v2.42.0 on November 2017, the
blobstore.options(at the root of the Agent settings JSON) are not used anymore by the Bosh Agent. So nowadays that no more supported Stemcell ships with older Agents, the CPIs should not add those properties anymore to the Agent settings.ERB unit tests have been added to provide proper coverage for the new use-case. Then can be run with:
Co-Authored-By: @ansh-SAP