Allow Direct Path Specification for Bicep Files in MicrosoftSecurityDevOps@1 Task

I am using the MicrosoftSecurityDevOps@1 task in my Azure pipeline to scan Infrastructure as Code (IaC) files. My repository contains multiple Bicep modules, each located in their own subfolders. Here is a snippet of my pipeline configuration:
parameters:

• name: serviceConnection
  type: string
• name: resourceGroup
  type: string
• name: bicepFile
  type: string
• name: parametersFile
  type: string

jobs:

• job:
  displayName: "Scan IaC Templates"
  pool:
  vmImage: windows-latest
  steps:
  • checkout: azure.infra.bicep
  • task: MicrosoftSecurityDevOps@1
    displayName: MSDO IAC
    inputs:
    categories: 'IaC'

The folder structure of my repository is as follows:
repo_name/
└── modules/
└── module-name/
└── module-name.bicep

Issue: Currently, there is no option to specify a direct path to a specific Bicep file within the MicrosoftSecurityDevOps@1 task. As a result, the tool attempts to scan absolutely all files being checked out, while I need to scan only the Bicep file specified in my parameters. This limitation makes it challenging to target individual Bicep files for scanning in repositories with complex structures and multiple modules.

Proposal: Introduce an option to specify a direct path to a specific Bicep file in the MicrosoftSecurityDevOps@1 task. This feature would allow for more targeted scanning of individual Bicep files.

Comienza por el manejo de entradas de la tarea MicrosoftSecurityDevOps@1 y su punto de entrada del escaneo de IaC/Bicep. Rastrea cómo se seleccionan los archivos extraídos y, a continuación, define la entrada de ruta directa solicitada mediante el parámetro bicepFile de la canalización. El trabajo estará terminado cuando la tarea pueda escanear un único archivo Bicep especificado sin escanear otros archivos extraídos.