Require all 3 osac e2e install checks on main - #153
Merged
Conversation
osac's own CI (vmaas/bmaas/caas full-install) has been live and passing on real PRs for a while now, but repo_osac's required_status_checks was left empty from before that CI existed -- meaning a PR could currently merge into osac:main with every check failing. Matches the pattern already enforced on fulfillment-service/osac-operator/osac-aap (one required check each), but requires all 3 e2e flavors here since this is now the repo everything actually merges into.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: osac-project/coderabbit/.coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
WalkthroughThe ChangesOSAC CI requirements
Estimated code review effort: 2 (Simple) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 11✅ Passed checks (11 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
repo_osac'srequired_status_checkswas left empty in Terraform with a comment explaining osac had no CI yet at the time it was created. That's stale now: osac's own e2e-vmaas/e2e-bmaas/e2e-caas full-install workflows have been running and passing on real PRs for a while.gh api repos/osac-project/osac/branches/main/protectioncurrently returnsrequired_status_checks: null-- a PR can merge intoosac:maintoday even with every check failing.Verification
tofu fmt -check -diff: clean.tofu validate(aftertofu init -backend=false): valid, no new warnings (25 pre-existing unrelated deprecation warnings only).plan/applyneeds the S3 backend's CI credentials -- not runnable locally, same as every prior PR in this repo; relies on the existing apply pipeline.Test plan
gh api repos/osac-project/osac/rulesetsshows the newci-status-checksruleset with all 3 contextsSummary by CodeRabbit
repo_osacmodule to include all OSAC end-to-end checks: VMAAS, BMAAS, and CAAS.