Skip to content

Follow the bosh-deployment default branch - #11

Open
aramprice wants to merge 1 commit into
cloudfoundry:mainfrom
aramprice:codex/bosh-deployment-main
Open

aramprice wants to merge 1 commit into
cloudfoundry:mainfrom
aramprice:codex/bosh-deployment-main

Conversation

@aramprice

@aramprice aramprice commented Nov 3, 2026 •

Copy link
Copy Markdown
Member

Remove the explicit master selector from read-only bosh-deployment Git sources, allowing them to follow the repository default before and after its rename. These changes can be merged and applied while the default is still master.

Concourse Git resource contract: a read-only source can follow the default by omitting branch; a write source requires an explicit branch.

Validation: git diff --check passed. Exact parsed before/after comparison confirms only the intended Git source branch selectors changed. Modern strict offline pipeline validation reports the same existing template/legacy-schema errors before and after; runtime compatibility requires operator verification.

Only checked-in definitions are changed. Deployed pipeline reconfiguration and runtime checks remain operator-owned. No Concourse pause/unpause, configuration, cache clearing, resource checks, job triggers or configure-script execution were performed.

Cutover steps, consumer readiness and rollback: cloudfoundry/bosh-deployment#539

Community configuration (draft): cloudfoundry/community#1686

@aramprice

Copy link
Copy Markdown
Member Author

Feel free to merge and reconfigure at any time. Since this is a read-only resource the default branch will be used, regardless of name.

@aramprice

Copy link
Copy Markdown
Member Author

PSA: the master => main cutover will likely happen Nov 4th or 5th

@aramprice

Copy link
Copy Markdown
Member Author

bosh-deployment default branch has been cut over from master => main

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant