Since results.json and filtered_results.json are hardcoded in the code of the Pipeline Action Scan, and code responsible for their respective parameters is commented out, they will always show up after a scan. This is contradictory to the description of the parameters, and the following parameters don't work because of this:
json_output
json_output_file
filtered_json_output_file
Issue nr 1:
When we simply add "json_output: false" the job crashes like this:
Issue nr 2:
If we simply change the name with "json_output_file: somethingelse.json"
The action simply disregards this and still produces results.json and uploads it as a GitHub artifact, and somethingelse.json is nowhere to be found.
For now, the only way I found to obscure those files in to set summary_output_file: results.json to overwrite that file with the human readable summary file.
Since
results.jsonandfiltered_results.jsonare hardcoded in the code of the Pipeline Action Scan, and code responsible for their respective parameters is commented out, they will always show up after a scan. This is contradictory to the description of the parameters, and the following parameters don't work because of this:Issue nr 1:
When we simply add "
json_output: false" the job crashes like this:Issue nr 2:
If we simply change the name with "
json_output_file: somethingelse.json"The action simply disregards this and still produces results.json and uploads it as a GitHub artifact, and
somethingelse.jsonis nowhere to be found.For now, the only way I found to obscure those files in to set
summary_output_file: results.jsonto overwrite that file with the human readable summary file.