-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: ensure tokens consistency after editing and redeploying. #3768
base: main
Are you sure you want to change the base?
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.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @mtalvi. Thanks for your PR. I'm waiting for a opendatahub-io member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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 kubernetes-sigs/prow repository. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3768 +/- ##
==========================================
- Coverage 84.63% 84.62% -0.01%
==========================================
Files 1515 1515
Lines 35100 35110 +10
Branches 9814 9820 +6
==========================================
+ Hits 29707 29713 +6
- Misses 5393 5397 +4
... and 6 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
/ok-to-test |
If you add a space in the model name it will fail, I believe it's because |
Related to the following:
https://issues.redhat.com/browse/NVPE-154
https://issues.redhat.com/browse/NVPE-156
Description
Fix to ensure tokens consistency after editing and redeploying.
How Has This Been Tested?
Tested locally.
Test Impact
There are 2 main scenarios to be checked:
Model was initially deployed without any tokens and token authentication was added via edit:
Model was initially deployed with token authentication and another new token was added via edit:
Screenshot of the relevant dashboard:

Request review criteria:
Self checklist (all need to be checked):
If you have UI changes:
After the PR is posted & before it merges:
main