Add attack track controls to gitRegoStore #560
YiscahLevySilas1pr-tests.yaml
on: pull_request
Build and test rego artifacts
4m 35s
test_pr_checks
/
check if secrets are set
0s
test_pr_checks
/
Create cross-platform build
12m 58s
markdown-link-check
13s
test_pr_checks
/
Basic-Test
5m 57s
Matrix: ks-and-rego-test / run-tests
Remove pre-release folder and clean up
0s
Annotations
5 errors and 2 warnings
|
Build and test rego artifacts
Process completed with exit code 2.
|
|
test_pr_checks / Basic-Test
Bad response: 500 {"message":"Build processing error.","error":true,"url":""}
|
|
test_pr_checks / Basic-Test:
gitregostore/gitstoreutils.go#L218
S1009: should omit nil check; len() for []github.com/kubescape/opa-utils/reporthandling.AttackTrackCategories is defined as zero (gosimple)
|
|
test_pr_checks / Basic-Test
issues found
|
|
test_pr_checks / Basic-Test
Process completed with exit code 1.
|
|
test_pr_checks / Create cross-platform build
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
|
|
test_pr_checks / Create cross-platform build
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.14.1.
|