Replace dyn_client with client in all get calls#980
Replace dyn_client with client in all get calls#980dbasunag merged 2 commits intoopendatahub-io:mainfrom
Conversation
|
The following are automatically added/executed:
Available user actions:
Supported labels{'/build-push-pr-image', '/hold', '/cherry-pick', '/lgtm', '/verified', '/wip'} |
📝 WalkthroughWalkthroughKeyword argument refactor: multiple test utilities and fixtures updated to pass the Kubernetes client as Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used🧬 Code graph analysis (1)tests/model_registry/model_catalog/conftest.py (2)
🔇 Additional comments (1)
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 |
There was a problem hiding this comment.
Actionable comments posted: 0
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
tests/model_registry/scc/utils.py (1)
98-104: This change is incomplete and will cause runtime failures.While the update from
dyn_clienttoclientinPod.get()is correct, the parameter rename is incomplete across the codebase. A search reveals 40+ remainingdyn_client=usages in:
- utilities/operator_utils.py, mariadb_utils.py, jira.py, kueue_utils.py, infra.py, inference_utils.py, general.py
- conftest.py and test fixture files throughout tests/
If the method signatures have been changed from
dyn_client=toclient=globally, these remaining calls will fail at runtime. All occurrences must be updated consistently.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (9)
tests/model_registry/async_job/utils.pytests/model_registry/conftest.pytests/model_registry/image_validation/conftest.pytests/model_registry/model_catalog/utils.pytests/model_registry/rest_api/test_model_registry_rest_api.pytests/model_registry/rest_api/test_multiple_mr.pytests/model_registry/rest_api/utils.pytests/model_registry/scc/utils.pytests/model_registry/utils.py
🧰 Additional context used
🧬 Code graph analysis (9)
tests/model_registry/model_catalog/utils.py (2)
tests/model_registry/conftest.py (1)
model_registry_namespace(76-77)tests/conftest.py (1)
admin_client(79-80)
tests/model_registry/rest_api/utils.py (1)
tests/conftest.py (1)
admin_client(79-80)
tests/model_registry/scc/utils.py (1)
tests/conftest.py (1)
admin_client(79-80)
tests/model_registry/rest_api/test_model_registry_rest_api.py (2)
tests/conftest.py (1)
admin_client(79-80)tests/model_registry/conftest.py (1)
model_registry_namespace(76-77)
tests/model_registry/image_validation/conftest.py (1)
tests/conftest.py (1)
admin_client(79-80)
tests/model_registry/conftest.py (1)
tests/conftest.py (1)
admin_client(79-80)
tests/model_registry/async_job/utils.py (1)
tests/conftest.py (1)
admin_client(79-80)
tests/model_registry/rest_api/test_multiple_mr.py (2)
tests/model_registry/conftest.py (1)
model_registry_namespace(76-77)tests/conftest.py (1)
admin_client(79-80)
tests/model_registry/utils.py (2)
tests/conftest.py (1)
admin_client(79-80)tests/model_registry/conftest.py (1)
model_registry_namespace(76-77)
🔇 Additional comments (11)
tests/model_registry/async_job/utils.py (1)
18-23: LGTM!The keyword argument update from
dyn_clienttoclientis correct and aligns with the updated API parameter naming.tests/model_registry/rest_api/utils.py (1)
267-268: LGTM!The keyword argument change from
dyn_clienttoclientin theDeployment.getcall is correct and maintains the function's behavior.tests/model_registry/model_catalog/utils.py (2)
30-32: LGTM!The keyword argument update from
dyn_clienttoclientin theRoute.getcall is correct.
47-51: LGTM!The keyword argument update from
dyn_clienttoclientin thekind.getcall is correct and maintains the validation logic.tests/model_registry/image_validation/conftest.py (1)
29-34: LGTM!The keyword argument update from
dyn_clienttoclientin thePod.getcall is correct.tests/model_registry/rest_api/test_model_registry_rest_api.py (1)
161-161: LGTM! Parameter name updated correctly.The keyword argument change from
dyn_clienttoclientaligns with the updatedPod.getAPI signature.tests/model_registry/rest_api/test_multiple_mr.py (1)
62-62: LGTM! Parameter name updated correctly.The keyword argument change from
dyn_clienttoclientaligns with the updatedConfigMap.getAPI signature.tests/model_registry/utils.py (3)
67-67: LGTM! Parameter name updated correctly.The keyword argument change from
dyn_clienttoclientinService.getaligns with the updated API signature.
249-249: LGTM! Parameter name updated correctly.The keyword argument change from
dyn_clienttoclientinPod.getaligns with the updated API signature.
666-666: LGTM! Parameter name updated correctly.The keyword argument change from
dyn_clienttoclientinPod.getaligns with the updated API signature.tests/model_registry/conftest.py (1)
636-636: Parameter change verified correctly. The keyword argument inRoute.get()has been successfully updated fromdyn_clienttoclientat line 636. Verification confirms no remainingdyn_clientusages in the model_registry test files.
2f10e6d to
8c57878
Compare
|
Status of building tag latest: success. |
Description
How Has This Been Tested?
Merge criteria:
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.