RHAIENG-1795: test using gateway config as fallback for constructing dashboard url#993
Conversation
|
@kryanbeane: This pull request references RHAIENG-1795 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set. DetailsIn response to this:
Instructions 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 openshift-eng/jira-lifecycle-plugin repository. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #993 +/- ##
==========================================
+ Coverage 96.46% 96.47% +0.01%
==========================================
Files 23 23
Lines 2318 2329 +11
==========================================
+ Hits 2236 2247 +11
Misses 82 82 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Cover the new GatewayConfig hostname resolution path to satisfy codecov/patch coverage requirements.
77acaf7 to
9809694
Compare
The GatewayConfig fallback code calls get_cluster_custom_object, which was previously unmocked in the "no hostname" test cases. On CI, the unmocked call could return stale data instead of raising, causing the test to get a URL when it expected None.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pawelpaszki The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Issue link
RHAIENG-1795
What changes have been made
Added fallback to use gateway config for constructing dashboard url
Verification steps
Hard to verify - @CathalOConnorRH has verified I believe that without usual gateway object, this works as an alternative
Checks