Today, the action reports the result of the "validation" in the output of the pipeline, and it raises/publishes the results to the "portal".
But, in the GitHub Actions pipeline, then it just "succeeds" even if "issues are found".
I.e. we cannot use the action, as is, to protect our pipelines, i.e. to the break the build, if any "violations" are found.
It would be useful with an option, where the plugin fails the build, if any "violations" are found, even for non PR builds.
I mean, it could be that a "security concern" has been registered/discovered, after the original PR were raised and approved. We want the plugin to be able to protect our pipelines in these scenarios as well, e.g. on deployments, so a deployment cannot take place, if contains "violations" that we discovered after the original PR.
Today, the action reports the result of the "validation" in the output of the pipeline, and it raises/publishes the results to the "portal".
But, in the GitHub Actions pipeline, then it just "succeeds" even if "issues are found".
I.e. we cannot use the action, as is, to protect our pipelines, i.e. to the break the build, if any "violations" are found.
It would be useful with an option, where the plugin fails the build, if any "violations" are found, even for non PR builds.
I mean, it could be that a "security concern" has been registered/discovered, after the original PR were raised and approved. We want the plugin to be able to protect our pipelines in these scenarios as well, e.g. on deployments, so a deployment cannot take place, if contains "violations" that we discovered after the original PR.