We validating the security scan config appropriately when
a version was already present in the skip list. This now
ensures a version exists before verifying that it contains an array.
We were also replacing the existing skip object in the
security-scan-config which prevented us from storing
multiple versions at a time. We now extend the object
instead using the spread operator.
rancher/rancher#24733rancher/rancher#24742
When the user doesn't have access to the systemProject we just
return an empty configMap so the page can proceed without error.
We also disable the runScan button if the systemProject isn't available.
rancher/rancher#24644
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
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
Because the scan will ignore an invalid config map I'm removing
the validation from run scan so the UI can run the scan without issue.
rancher/rancher#24496
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
If the security-config map wasn't present the detail view wouldn't work
properly. To resolve this we now create a new config map if it's not
present.
rancher/rancher#24432
This will ensure the user is notified when there's a json
parsing error of their security-scan-cfg config map.
The notification will happen during page load and if
they attempt to skip/unskip.
rancher/rancher#24417
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
Cody Jackson