-
Notifications
You must be signed in to change notification settings - Fork 261
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
Clone of global admin role not a 100% carbon copy #12052
Comments
@richard-cox changing the client version to v2.8.6 still clones an admin correctly, I suppose this is a server issue? |
@cnotv It looks like it's showing the bug. The verbs have been enumerated from |
I see the same for 2.9.x and even for the same Administrator. I do not understand what should be displayed. |
The An entry to that Or it could be The component that's showing a grant resource row isn't showing the |
Oh ok, in the model/YAML, I thought in the |
These 2 cases are the same but have different logic and URLs, so there's something wrong with the whole concept of editing in Rancher:
Refreshing the page and keeping the YAML editor is also impossible since it redirects to the configuration. |
Here is a summary of what I reported today: the whole resource editing process has a logic where data initialization is injected into YAML, without providing a way to restore the mapping (like from In the video, you can see how the roles are always manipulated and cannot be restored if edited in the form. As an outcome of this logic, we want to instead map the whole list of verbs always into Edit: I've replaced the video starting from Admin, so it's more evident the problem. |
I don't think we want to map anything to anything, that's the issue. If there's a The bug is we're converting a |
We must map it for sure, because we do not have a UI for |
I'm not quite sure i follow. I had a look, this is the code that maps * to the list of verbs https://github.com/rancher/dashboard/blob/master/shell/components/auth/RoleDetailEdit.vue#L130-L134. We just need to not do this, and also ensure |
Define valid entry, if you do not mind. |
Valid entry in the select component. The PR won't work because it's mapping * to a list of verbs. Lets get together after the team meet to go over this |
Updated PR as agreed in the meeting #12235 |
While this is set for v2.10, can we get backports into v2.8 and v2.9? |
v2.8 is EOM, v2.9 is a possibility though |
Clone of global admin role is properly copied. Tested in:
Screen.Recording.2024-10-18.at.6.29.18.PM.mov |
Jira: SURE-8806
Setup
Describe the bug
Clone of global admin role not exact copy. (Displayed as
Administrator/admin
)Where the original role has verbs "*" the copy has a list of individual verbs.
The result is new role does not grant the same views as the original.
To Reproduce
Result
The clone role does not have "*" verbs as in the original global admin role.
Note: This is about the data, so it's visible only in the YAML editor.
Expected Result
Expect a carbon copy.
Screenshots
See Jira ticket
Additional context
See Jira ticket
The text was updated successfully, but these errors were encountered: