Fix regression in creating registry creds. I misunderstood what willSave was
doing with the namespaceId when I added the ternary check. I simplified and
hopefully clarified what was actually happening when setting temp_id, now use
a local flag to set unset the temp namespace, then allow namespace to handle
saving or not saving the namespace.
rancher/rancher#27769
The modal was persisting the selection state between multiple
closing and openings of the modal. This now resets the selection
state.
rancher/rancher#27339
Object destructuring expects the entire object to be present. When
'Available to all namespaces in this project' is used the namespace
object isn't defined which causes the save to fail due to an null
exception.
rancher/rancher#26981
schemas do not reflect a default value and they are nullable
by placing min's on the input we don't allow the user to clear the input if they
want and because there are no defaults it doesn't make sense to place these
minimums on the input
rancher/rancher#27038
Not sure this every put registry secrets into the desired namespace. The
`namespaceId` was never set on the primaryResource by the namespace components,
rather those components worked on a namespace object. Ive gotten rid of
`namespaceId` and refactored to use the namespace object in its place.
rancher/rancher#26813
ProxyUrl could be empty. It will alwasy set a empty proxyUrl in alert
manger for the notifier. So alert manager cannot send out alerts due to
the empty proxy url setting.
https://github.com/rancher/rancher/issues/26089
- Label change for scheduled scans
- Fixed a table rendering bug that occured due to the incorrect value
of colspan
- Disabled the alert and scheduled scan button on the cis page for
windows clusters
- Fixed an issues where two scans couldnt run at the same time due
to a profile not being defined for a second run scan modal.
rancher/rancher#26009rancher/rancher#26021rancher/rancher#25987rancher/rancher#25983
- Added a Snapshot Now button to the top of the table
- Added a Restore Snapshot option to the actions of each row which will
select the current row when opening the modal
rancher/rancher#25511
We're removing the CIS skip button because we decided the current UX
is poort and we don't want to spend a tremendous amount of effort
making a marginally better UX in the short time we have left.
We also removed the 19 of 59 from the main CIS page as the total was
misleading and wasn't actionable.
rancher/rancher#25863
- Update the Available Snapshots labels
- Reverse the order of Available Snapshots
- Change 'Save' button to 'Restore' button
- Add restoration type section 'etcd', 'kubernetes version', 'etcd and
kuberneters version'
rancher/rancher#25525
This required refactoring the drain modal into a reusable component
since these fields were going to be used in more than one place.
rancher/rancher#24110
If nodes have been deleted previous reports with missing nodes were
breaking. To resolve that we now only show links to nodes that we can
find.
rancher/rancher#24676
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
while reviewing rancher/ui#23993 i stumbled on a case where opening the pod logs
would cause an undefined error to crash the local ui server. `exec` is called
correctly from the `watchReconnect` observer which needs to happen first as it
parses the container name. If we call exec before we have a container name we
get an undefined error
The keys for custom attributes needed to be unique. To enforce the
unique constraint I created the FormContextualKeyValue component.
This component behaves similarly to the FormContextualSelectArray
but handles key value pairs.
rancher/rancher#23782
When editing both single and multi-cluster apps if you modified the
Template Version or the Target Projects and then cancelled it the
underlying store was still modified which then reflected those changes
on other pages like the single and multi-Cluster Apps pages.
To change this I cloned and nested the fields into a nested object named
'editable' and updated the primarySource on willSave for the relevant
targets subfield.
rancher/rancher#21228