[aramprice]

WHAT is this change about?

The read-only bosh-deployment Git resource follows its default branch by omitting branch: master; related documentation links point to main. This PR targets develop under the contribution policy.

What customer problem is being addressed?

Release Integration CI needs to keep fetching bosh-deployment when its default branch is renamed to main. The selector works before and after rename.

Context

Cutover issue: cloudfoundry/bosh-deployment#539

Community draft: cloudfoundry/community#1686

Has this passed cf-acceptance-tests?

• YES
• NO — no live deployment or CAT run for this CI-selector/documentation change.

Does this introduce a breaking change?

• YES
• NO — deployment manifests, ops files, variables and release versions are unchanged.

Release notes

CI follows the default branch of bosh-deployment.

New BOSH release?

• YES
• NO

Experimental or GA component?

Not applicable: CI and documentation maintenance.

Acceptance criteria and validation

Validation: git diff --check passed. Exact parsed before/after comparison confirms only the intended Git source branch selectors changed. Local strict pipeline validation passed. All eight packages in the repository local interpolation suite (./units/test) passed; no live deployment or CAT run was performed. The owning operator stages the read-only selector and confirms the resource fetches the target default before and after rename. No deployed pipeline changes were performed by this work.

Urgency

• Urgent — stage active CI consumers before the target rename.
• Slightly less than urgent

Pair / team

Not applicable.

[ard-wg-gitbot]

Hello friend, it looks like your pull request has failed one or more of our checks. Please take a look! 👀