Run CIS Scan was broken on the cluster list page because
currentCluster was being used instead of just using the current cluster.
I also removed the redirect and just use a growl notification to
indicate the scan is running.
rancher/rancher#25241rancher/rancher#25159
Improving the UX of CIS based on the feedback that was received during
the review.
- Sort scans by date so newest will be on top.
- Details should be sorted by state in Fail, Skipped, Pass order
- Add a Run CIS Scan action to the cluster menu.
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
This allows the id column to sort as if the ids are versions instead of
plain strings. This allows 1.1.2 to come before 1.1.10 when sorting.
rancher/rancher#24417
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
We want to provide the owner as additional information when showing
node templates on the node templates page. We also want to make it so
that when selecting a node template the users templates will be grouped
and sorted to the top by default.
rancher/rancher#23325
- Moved from Ember.$() to importing jquery.
- Moved from fn().on() to on(fn())
- Moved from fn().observes() to observer(fn())
This got /g/clusters from 27 warnings to 5 warnings for me.
We want to provide a quick way to delete unused cloud credentials.
To do this we're going to show the user the number of node templates
that each cloud credential is associated with.
rancher/rancher#23064
Remove ember object and use regular object instead
Found durning upgrade to 3.12, I'm not sure why we'd even need to declare an
ember object for this return anyway.
Get the current cluster's id from scope servervice
Found durning upgrade to 3.12, not sure how this ever worked as I looked on live
and it was failing but the system didn't explode on 3.8. In 3.12
transistion.params is undefined and the whole system explodes. We were never
passing the queryparams so they wouldn't have come through. I changed this so we
fetched the current cluster id from the scope service and everything seems to
work correctly.
Ensure that accordion items only try to expand once during the init
Found durning upgrade to 3.12, expanded was being double rendered.
lint fix
test fixes
lint
The cluster upgrade notification wasn't properly updating when
the user enabled and disabled a revision. It required that the
page was refreshed before display the fresh data.
This resolves this issue by watching more appropriate keys
int he relevant computed properties. The most relevant
being the revision.@each.enabled on the latestRevision property.
rancher/rancher#23126
- We will only conditionally render template/revision section on the
monitoring page if the cluster is using a template. This was
crashing the page before.
- We will now make sure there's a string when invoking replace
when generating the template and revision display names.
- We will now respect the enable flag of template revisions
when determining if an upgrade is available.
rancher/rancher#23126
We want to make it easier for someone that is managing multiple
clusters to see what template and template revision a cluster
is using. We also want to make it easy for a user to notice
that a cluster isn't using the latest revision.
To achieve this we added the template and revision to a column
in the clusters table to display both. We also indicate add
a warning badge beside a revision when the revision isn't
the latest.
rancher/rancher#22047
Editing was failing when an existing unsupported storage type had
already been used and the ferature flag unsupported-storage-drivers
was false. Adding a volume as part of a workload was also broken
when attempting to use an unsupported storage type.
To remedy this I decided to refactor the code and make the filtering
happen explicitly only for the dropdowns.
I also decided to make feature checking reusable and either to use
by adding a service to check if a flag is enabled.
rancher/rancher#22895rancher/rancher#22998
Cody Jackson
Westly Wright
loganhz
shanewxy
Westly Wright
LiuYan