[rhoai-2.25] fix(ci): require RHOAI Quay bot secrets in params-env#2559
[rhoai-2.25] fix(ci): require RHOAI Quay bot secrets in params-env#2559jiridanek wants to merge 1 commit into
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe Quay authentication workflow step now validates both required secrets at runtime, reports missing credentials, and exits unsuccessfully before attempting authentication. ChangesQuay authentication validation
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related issues
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 Checkov (3.3.8).github/workflows/params-env.yamlTraceback (most recent call last): Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/params-env.yaml:
- Around line 44-47: Reorder the workflow so the RHOAI_QUAY_BOT_USERNAME and
RHOAI_QUAY_BOT_PASSWORD validation runs before the “Unlock encrypted secrets
with git-crypt” step or any other secret-dependent setup. Preserve the existing
::error:: message and exit behavior, ensuring fork PRs receive the Quay-specific
failure before GIT_CRYPT_KEY is accessed.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 20d9740f-e892-4b50-be41-ae7970807498
📒 Files selected for processing (1)
.github/workflows/params-env.yaml
|
Created DevOps support request to update our secret after recent rotation. |
Fail loudly with ::error:: when secrets are missing instead of a broken optional if-guard; fork PRs without secrets are unsupported.
10a47dc to
2ba1c20
Compare
Description
Make Quay.io RHOAI bot login required in
params-envvalidation.if: env.RHOAI_QUAY_BOT_USERNAME != ''guard (step-levelenvis not visible toif, and unset ≠''so the step always ran).RHOAI_QUAY_BOT_USERNAME/PASSWORDare missing, fail with a loud::error::that fork PRs are unsupported (GitHub withholds repository secrets) and same-repo branches are required — aligned with CONTRIBUTING.md and Build Notebooks fork messaging.Independent of #2556.
How Has This Been Tested?
env/ifsemantics and existing fork guidance.Self checklist (all need to be checked):
make testdoes not exercise this GHA)rhoai-2.25(not an ODH sync path change)Merge criteria:
Test plan
::error title=Missing RHOAI Quay bot secrets::annotationSummary by CodeRabbit