ESLint + Unrecognized argument key: Extensions

[abjinugu]

Azure Pipeline Task

- task: MicrosoftSecurityDevOps@1
    displayName: 'Run Security Scan'
    inputs:
      categories: 'secrets, artifacts, containers, code'
      tools: 'trivy,eslint' 
      artifactName: 'CodeAnalysisLogs'
      config: '$(Build.SourcesDirectory)/.gdn/msdo-config-linux.gdnconfig'
      break: false

gdnconfig

{
  "tools": [
    {
      "tool": {
        "name": "trivy",
        "version": "latest"
      },
      "arguments": {
        "Action": "filesystem",
        "Target": "src/backend/api",
        "ExitCode": 100,
        "TableFormat": "sarif",
        "Scanners": "vuln"
      }
    },
    {
      "tool": {
        "name": "eslint",
        "version": "latest"
      },
      "arguments": {
        "ExclusionPatterns": "*.d.ts",
        "Targets": "src/ui"
      }
    }
  ]
}

error

##[error]Error running tool 2 of 2: eslint
##[error]UnrecognizedArgumentException: Unrecognized argument key: Extensions
##[error]BreakException: Guardian detected one or more breaking results.

[chrisnielsen-MS]

Hi @abjinugu - this error seems to suggest that the Extensions option is being included which is not valid for the latest version of ESLint. I am having trouble reproducing this, can you help me get some more information?

First off, in your Azure DevOps task logs there should be a command line of exactly what was run. It should look similar to this:
/home/vsts/work/_msdo/versions/Microsoft.Security.Devops.Cli.linux-x64.0.215.0/tools/guardian run -c /home/vsts/work/1/s/.config/eslint.gdnconfig -p azuredevops --tool eslint --rich-exit-code --logger-pipeline --export-file /home/vsts/work/1/a/.gdn/msdo.sarif --telemetry-environment azdevops

I'm looking to confirm the *.gdnconfig file you shared is indeed the one being used.

Are there any other files in your repository's .gdn folder?

[chrisnielsen-MS]

Hi @abjinugu, we have been unable to continue this investigation due to lack of response here. We are closing this issue, please re-open it or open a new one if you continue to experience this problem.