sonarqube2hdf output issues - null on mandtory fields

[Jiri-Stary]

I run sonarqube2hdf

`docker run --rm -w /share -v ${sarif_files_path}:/share -e SONAR_HOST_URL -e SONAR_TOKEN_GOLDENFROG mitre/saf:1.4.8 convert sonarqube2hdf -n ${{ inputs.SONAR_PROJECT_KEY || steps.sonar-properties.outputs.project-key}} -u $SONAR_HOST_URL --auth $SONAR_TOKEN -o ./hdf/sonarqube_scan.json "

`
and afterwards i need to manually modify couple fields so i can convert it to sarif

using :

        - name: SARIF Multitool
          if: ${{  always()  && steps.sonarqube-query-json.outcome == 'success' }}
          uses: microsoft/[email protected]
          with:
                # Command to be sent to SARIF Multitool
                command: 'convert  ./hdf/sonarqube_scan.json -t Hdf --output ./hdf/sonarqube_scan.sarif'

The issue:

sonarqube2hdf command is generating "null" where SARIF multitool expect a specific value.
My workround is to use sed and replace null with empty values which does work:

There are 2 problematic fields which are "mandatory" - version , code

"profiles": [
{
"name": "Sonarqube Scan",
"version": null,`

Could you take a look on this please?

[Amndeep7]

Thanks for bringing this to our attention @Jiri-Stary. We'll take a look.

[Amndeep7]

Hi @Jiri-Stary. It seems like the SARIF multi-tool currently has an issue which is making it impossible for me to test locally: "BUG: Fix ERR999.UnhandledEngineException: System.IO.FileNotFoundException: Could not find file when a file name or directory path contains URL-encoded characters.". We will need to wait until that bugfix is released before I can test any changes I make using that utility.