-
Notifications
You must be signed in to change notification settings - Fork 178
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
feat(mr settings): permissions table #2969
feat(mr settings): permissions table #2969
Conversation
0066695
to
f37ed0c
Compare
i just noticed the ? icon for the default group permission in the new mock and if i aggregate the previous mocks i need it to have a tooltip that says "This group is created by default. You can add users to this group via the API." so i'll add that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really good stuff @gitdallas . I have a couple of things, hopefully it won't be too bad to address.
frontend/src/concepts/roleBinding/RoleBindingPermissionsTableRow.tsx
Outdated
Show resolved
Hide resolved
frontend/src/concepts/roleBinding/RoleBindingPermissionsTableRow.tsx
Outdated
Show resolved
Hide resolved
f37ed0c
to
9836d03
Compare
@gitdallas while you're in here, can you actually also please look at the |
Looks like the test failure is just Prettier |
9836d03
to
bbc9a6f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and it's working well for me on the MR side, and the failures on the project side are caused by the lines I comment on below. Also a couple more minor nits. Otherwise all the changes LGTM.
frontend/src/concepts/roleBinding/RoleBindingPermissionsTable.tsx
Outdated
Show resolved
Hide resolved
frontend/src/concepts/roleBinding/RoleBindingPermissionsTable.tsx
Outdated
Show resolved
Hide resolved
frontend/src/concepts/roleBinding/RoleBindingPermissionsTableRow.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok I agree on @mturley changes and I added one more thing to do. Rest lgtm
36049a1
to
c7a782b
Compare
failing test seems unrelated (compareRuns graph) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, just a nit, rest of code looks great, once you have that change we can merge it!
frontend/src/pages/modelRegistrySettings/ModelRegistriesPermissions.tsx
Outdated
Show resolved
Hide resolved
c7a782b
to
ff4a46b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lucferbux The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
mmmm weird, some pipeline test has failed. let me try and retest it |
@lucferbux - yea, mentioned that #2969 (comment) seems consistent |
Signed-off-by: gitdallas <[email protected]> auto lint fixes Signed-off-by: gitdallas <[email protected]> fix lints Signed-off-by: gitdallas <[email protected]> some cleanup Signed-off-by: gitdallas <[email protected]> tests for mr permissions Signed-off-by: gitdallas <[email protected]>
Signed-off-by: gitdallas <[email protected]>
Signed-off-by: gitdallas <[email protected]>
Signed-off-by: gitdallas <[email protected]>
ff4a46b
to
d29d5e1
Compare
/lgtm |
Closes: https://issues.redhat.com/browse/RHOAIENG-6636
Description
Add model registry settings > permissions page. Factored out components from ProjectSharing (project permissions).
How Has This Been Tested?
Ran through creating/editing/deleting rolebindings for users/groups in model registries, also tested project permissions since that was factored out.
Test Impact
added cypress testing for the new page
Request review criteria:
make sure that you can create/edit/delete user/group rolebindings for model registries and that project permissions isn't broken
Self checklist (all need to be checked):
If you have UI changes:
After the PR is posted & before it merges:
main