security: re-enable security scan release block

This was previously disabled due to an unresolved false-positive CVE.
Re-enabling both secrets and OSV + Go Modules scanning, which per our
current scan results should not be a blocker to future releases.
zalimeni/enable-security-scans-release--test
Michael Zalimeni 12 months ago
parent ae998a698a
commit bbfb381534

@ -1,17 +1,33 @@
# Copyright (c) HashiCorp, Inc. # Copyright (c) HashiCorp, Inc.
# SPDX-License-Identifier: BUSL-1.1 # SPDX-License-Identifier: BUSL-1.1
# These scan results are run as part of CRT workflows.
# Un-triaged results will block release. See `security-scanner` docs for more
# information on how to add `triage` config to unblock releases for specific results.
# In most cases, we should not need to disable the entire scanner to unblock a release.
# To run manually, install scanner and then from the repository root run
# `SECURITY_SCANNER_CONFIG_FILE=.release/security-scan.hcl scan ...`
# To scan a local container, add `local_daemon = true` to the `container` block below.
# See `security-scanner` docs or run with `--help` for scan target syntax.
container { container {
dependencies = true dependencies = true
alpine_secdb = false alpine_secdb = false
secrets = false
secrets {
all = true
}
} }
binary { binary {
secrets = false go_modules = true
go_modules = false
osv = true osv = true
# TODO(spatel): CE refactor
oss_index = true oss_index = true
nvd = true nvd = true
secrets {
all = true
}
} }

Loading…
Cancel
Save