You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Follow AWS CPI and certification default branches (ubuntu-jammy) - #788
The read-only AWS CPI and CPI certification Git sources will follow their repositories' default branches. Both selectors can be applied while those defaults are still master and will follow main after the renames.
Validation: git diff --check passed. Parsed before/after comparisons confirm only the intended Git branch selectors changed. Local fly validate-pipeline --strict passed on the rendered YTT template.
Default-following consumer changes can be merged and, where deployed, applied by their operators before the target rename.
This PR changes checked-in files only. Deployed pipeline reconfiguration and runtime checks remain operator-owned; no Concourse pipelines or jobs were modified, paused, unpaused, or triggered for this work.
No actionable comments were generated in the recent review.
Walkthrough
The bosh-cpi-certification-concourse-tasks and bosh-aws-cpi-release Git resources no longer specify branch: master. They now use their repositories’ default branches.
Suggested reviewers: mkocher
Merge Risk: Minimal · up to 75353
The read-only AWS CPI and certification sources will follow their repositories’ default branches. No current incompatibility is established; the change is mergeable subject to normal validation and operator-owned pipeline reconfiguration.
Pre-merge checks: 3 · 1
Failed checks: 1 warning
Check name
Status
Explanation
Resolution
Description check
The description clearly explains the change, validation results, scope, operator-owned work, and cutover plans. It does not include the required Merge Forward section with the target branch and merge-…
Add the required Merge Forward section. State the oldest applicable target branch for this PR and confirm the merge-forward chain. Add the AI Review Feedback section and resolve or explain any applicable AI review comments.
Passed checks: 3 passed
Check name
Status
Explanation
Title check
The title names two real changes in the diff: the AWS CPI and CPI certification Git resources now follow default branches instead of pinning master. It omits the purpose and the ubuntu-jammy reference…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Title check
Explanation
The title names two real changes in the diff: the AWS CPI and CPI certification Git resources now follow default branches instead of pinning master. It omits the purpose and the ubuntu-jammy reference is not clearly tied to the diff, but it describes the main change accurately and is specific.
Full details: Description check
Explanation
The description clearly explains the change, validation results, scope, operator-owned work, and cutover plans. It does not include the required Merge Forward section with the target branch and merge-forward chain, or the AI Review Feedback section from the repository template.
Resolution
Add the required Merge Forward section. State the oldest applicable target branch for this PR and confirm the merge-forward chain. Add the AI Review Feedback section and resolve or explain any applicable AI review comments.
Finishing Touches
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Warning
Some tools did not complete. Review the errors below.
ast-grep (0.51.1)
ast-grep could not parse rule config: /ast-grep-rules/ast-grep-essentials/rules/ruby/security/dynamic-constantize-params-ruby.yml
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Run CodeRabbit Verify to test the changes in this pull request.
Recent review info
Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: ASSERTIVE
Plan: Advanced
Run ID: 69b5f35a-0615-46f3-8fd1-0858427bd20d
Commits
Reviewing files that changed from the base of the PR and between 25f9800 and 75353fd.
Files selected for processing: 1
ci/pipeline-template.yml
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The read-only AWS CPI and CPI certification Git sources will follow their repositories' default branches. Both selectors can be applied while those defaults are still
masterand will followmainafter the renames.Validation:
git diff --checkpassed. Parsed before/after comparisons confirm only the intended Git branch selectors changed. Localfly validate-pipeline --strictpassed on the rendered YTT template.Default-following consumer changes can be merged and, where deployed, applied by their operators before the target rename.
Concourse Git resource contract: a read-only source can omit
branch; a source used forputneeds an explicit branch.This PR changes checked-in files only. Deployed pipeline reconfiguration and runtime checks remain operator-owned; no Concourse pipelines or jobs were modified, paused, unpaused, or triggered for this work.
Cutover plans:
Shared community configuration (draft): cloudfoundry/community#1682