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
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
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