Fix handling of Defcon 1

Fixes #1397
This commit is contained in:
Joseph Schorr 2016-04-22 13:21:35 -04:00
parent 460ccf2dfd
commit 34a8090328
5 changed files with 5 additions and 5 deletions

View file

@ -115,6 +115,6 @@
}
.image-feature-view-element .defcon1 {
background-color: #FF8181;
background-color: #FB5151;
color: white;
}

View file

@ -199,6 +199,6 @@
}
.image-vulnerability-view-element .defcon1 {
background-color: #FF8181;
background-color: #FB5151;
color: white;
}

View file

@ -21,7 +21,7 @@
<div class="co-alert co-alert-danger" ng-if="hasDefcon1">
One or more of your tags has an <strong>extremely critical</strong> vulnerability which should be addressed immediately:
<a href="{{ vuln.Link }}" ng-repeat="(key, vuln) in defcon1" style="margin-left: 10px;" target="_blank">
{{ vuln.ID }}
{{ vuln.Name }}
</a>
</div>

View file

@ -168,7 +168,7 @@ angular.module('quay').directive('repoPanelTags', function () {
VulnerabilityService.forEachVulnerability(resp, function(vuln) {
if (VulnerabilityService.LEVELS[vuln.Severity].index == 0) {
$scope.defcon1[vuln.ID] = v;
$scope.defcon1[vuln.Name] = vuln;
$scope.hasDefcon1 = true;
}

View file

@ -78,7 +78,7 @@ PRIORITY_LEVELS = {
'description': 'Critical is a world-burning problem, exploitable for nearly all people in ' +
'a installation of the package. Includes remote root privilege escalations, ' +
'or massive data loss.',
'banner_required': True
'banner_required': False
},
'Defcon1': {