When adding input-yaml to a modal it required the user to click on
the input before the value would be loaded and the editor resized.
I found a github issue which suggested making use of the isVisible
property to force a refresh so I added the use of it to force refreshing
to happen.
I also made it so the header didn't add a margin if the header wasn't
present.
The downloaded report now has:
- A column for passed_nodes
- A column for failed_nodes
- A column for all nodes the test ran against
- The benchmark version in the header
rancher/rancher#24671
I don't want to validate the configMap in the skipList
because a malformed configMap is the equivelant of
an empty skipList for the purposes of running a scan
and displaying what is currently being skipped.
rancher/rancher#24627
The security-scan-config wasn't being reloaded when
navigating between clusters because the config map
was getting cached. This forces it to be reloaded.
rancher/rancher#24623
The new API required that I pass null instead of an empty array
as the skiplist if nothing is supposed to be skipped when
running a scan.
Updated the color of the running state to info instead of success
as requested.
We provide an error notification when the security config is malformed and
the user attempts to run a scan. We also prevent the scan from running.
We also added a default sort by 'id' on the scan detail table.
rancher/rancher#24495rancher/rancher#24496
rancher/rancher#23452
expose link-to new-group route
Translations change and move static property (convention)
Refactor form-global-roles
Refactor such that user and group are optional parameters. Adds
groupPrincipalId. Destructure smarter so that users are not required for the
mapper function to work. Move bindings to own init. Refactor make to recognize
groups. Translations changes.
Add cru-group-account component
This component does not actually create a group but a global-role-binding with a
groupPrincipalId instead of a userId. Perhaps cru-global-role-binding would work
but in the future this component can and probably will be adapted to create
local groups as well, so the name would fit. At that point the component could
also be refactored to work for the add user page because at that point pretty
much doing the same thing but that is not with-in the scope of this change.
Currently the componet is expected to be used with an auth provider that
supports groups which is why it does not also create the group. This should be
taken into consideration if we ever update this to work with local groups.
Translations changes.
formatting
wip
Add tab nav template only component
rename users index route -> users & add groups route
get groups from grb list and build groupPrincipal list
Add role binding to the fetched group principal
Add account-group-row component and define table row views
global role binding with group edit page
Fix transitionTo in cancel and doneSaving -> cru-group-account
translations
Add initialPrincipal param to input-identity to allow use on edit
reduce duplicate principal calls and display on groups list page
fix role links types from account-group-row
add group delete functionality
translations and bulk action fix
sort global role names in modal and row
delete GRB modal translations
move users route to security-> users, break out groups route security
remove unneeded component
Live update fixes
translation fix
fix broken link to old accounts route
remove unneeded props, angle bracket components, general cleanup
lint fixes
Change add group button
Add warning on add group for non-local auth only and translations
Remove warning from delete group modal and change translations
re-org form-global-roles display
breaks the display out into base|user-custom|additional roles
adds back in details & descriptions
fixes role ids in translations file
`templateChanged` which loads the content of what we need for a MC app was
updated to watch a new property, `editable: { selectedTemplateUrl } `. The new
property was declared on the component as a object. Observers watching a static
object and that have never been fetched do not recompute. If we set the property
on init to the object it would have been declared with then additional sets on
the watched property cause the observer to recompute.
rancher/rancher#24057
When using an older vsphere node template in the latest version it was
possible that a user entered value would not be a valid option. When
the value isn't a valid option the dropdown has nothing selected. To
improve the UX we now notify the user that the current value is no
longer valid and sask them to select a new value.
rancher/rancher#23920
While working on a ticket to provide the ability to de-select subnetworks when
using the create subnetwork option I discovered the options were all messed up
and allowed you to misconfigure yourself into a hole.
I've moved ipalias and related networks settings out of advanced becuase
depending on what you select for your subnetwork the ability to choose ipalias
and the other settings changes.
This change allows you deselect a node subnet so you can create a subnetwork
automatically.
rancher/rancher#21079
Cody Jackson
Westly Wright
Westly Wright
Vincent Fiduccia
loganhz
Sebastiaan van Steenis