ROX-34000: fix reencrypt route with custom cert#19876
ROX-34000: fix reencrypt route with custom cert#19876rhacs-bot wants to merge 1 commit intorelease-4.10from
Conversation
|
Images are ready for the commit at 2576a81. To use with deploy scripts, first |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release-4.10 #19876 +/- ##
================================================
- Coverage 49.35% 49.34% -0.01%
================================================
Files 2661 2661
Lines 200825 200825
================================================
- Hits 99114 99104 -10
- Misses 94273 94278 +5
- Partials 7438 7443 +5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
/retest |
|
@rhacs-bot: The following test failed, say
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. |
Added PR reference tracking to show which PRs link to each Jira issue that has missing metadata. Example output: - ROX-33451: ✗ fixVersion, ✗ affectedVersion (Assignee: ..., Team: ..., Component: ...) (PRs: #19382) - ROX-34000: ✗ fixVersion, ✗ affectedVersion (Assignee: ..., Team: ..., Component: ...) (PRs: #19876, #19877) Implementation: - Track jira_key → PR numbers mapping while checking metadata - Include PR links at end of Jira issue line - Multiple PRs shown as comma-separated list with links Makes it easier to identify which PRs need Jira metadata updates. Partially generated with AI assistance.
Backport 27bf450 from #19866.