Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. WalkthroughThe configuration moves the ChangesSecret collection ownership
Priority: ⬆️ High Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to The ownership transfer is complete and leaves the secret collection operationally defined, so the change is ready to merge. 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: cubismod 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 |
|
[REHEARSALNOTIFIER] Note: If this PR includes changes to step registry files ( |
|
@cubismod: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
@cubismod can you please update it to claim the other quay secrets as well? |
|
/hold |
#84747 moved quay-tests secret group to be unclaimed as there was no rover group associated with this.
This PR stakes an ownership claim for
quay-develthe Quay.io upstream & downstream teams.https://redhat.atlassian.net/browse/QUAYIO-2267
This is necessary for updating our orion credentials which have been rotated due to a leak.
Summary by CodeRabbit
quay-testssecret collection to thequay-develRover group.