- See #2525
- Move descriptions into checkbox, handle size, colour and placement inside component
- Colour of label is a standard form colour, so in this case override it locally
- Addresses #2453
- ResourceTabs were previously exclusively used in detail pages which are
always `view` (there's some checks for view in there already, so this
might not have always been the case).
- PVC _edit_ component now uses ResourceTabs, so ResourceTab needs to take
into account view mode
- Update Users list with actions
- Add User create/edit page
- Add User details page
- Brought over user/principal global role validation from ember world
- edit yaml didn't show yaml because a schema wasn't defined
- edit yaml didn't save because the update link wasn't correct
- saving yaml didn't update the models in the stores
- not all input elements were passed the mode when looking at the config view
- the select and array list components had visual issues in view mode (didn't show the values and the buttons didn't line up well)
- cloning failed due to cleanForNew not accounting for the template property
https://github.com/rancher/dashboard/issues/2111#issuecomment-777066167
- Also fixed some mode issues with ArrayListGrouped that showed up on the view of these pages. Still need more tweaking to make it look good though.
rancher/dashboard#1818
- The first issue was caused by the introductions of ArrayListGrouped and not updating all references appropriately
- The other was caused by LabeledSelect calling the @input handler twice for every selection. The handler was toggling which caused the value to always reset. It looks like the reason labeled select was calling the handler twice was because of having both v-bind="$attrs" and @input="...". So i removed @input and verified that LabeledSelect still works for both v-model and value/@input.
rancher/dashboard#2211
- Add groups page with table to the auth product
- Allow user to assign roles to groups previously without roles or edit
groups with existing roles
Comments
- I haven't added any special ux for the case where there's no auth
provider and therefore no groups
- ./components/GlobalRoleBindings.vue will be updated when the same
component is used for assign global roles to a user principal
- ./components/GlobalRoleBindings.vue ln 139 Couldn't create a binding
without the generateName metadata property. Have given this a
`ui-` prefix. Is this correct?
- In order to determine which global roles are bound to each principal
(so we can filter by principals that have them).. we go out and fetch
ALL role bindings. Is this too costly?
- On the groups page the 'refresh' button is quite big, we should
consider reducing this