Migration from explicit inputs to configuration file for multiple repositories in single pipeline

To resolve the warnings regarding migration of the inputs we ran into a couple of issues.

The first is already covered in #327

The other problem that we have is that we use a single Azure DevOps pipeline to run the DependaBot task for multiple repositories in our project, for example:

steps:
  - task: dependabot@1 
    displayName: Dependabot | API
    inputs:
      packageManager: 'nuget'
      azureDevOpsAccessToken: $(pat)
      directory: api/
      targetRepositoryName: 'ado-project/api/'
      setAutoComplete: true
      extraEnvironmentVariables: AZURE_PROJECT=ado-project

  - task: dependabot@1
    displayName: Dependabot | Webapps
    inputs:
      packageManager: 'npm'
      azureDevOpsAccessToken: $(pat)
      directory: 'webapps/'
      targetRepositoryName: 'ado-project/webapps'
      setAutoComplete: true
      extraEnvironmentVariables: AZURE_PROJECT=ado-project

How would we differentiate between the multiple repositories that we are targeting on our pipeline?

[mburumaxwell]

@mburumaxwell just to clarify: this pr fixes that you can now use targetRepositoryName and useConfigFile and it will look for that config file in the repository of targetRepositoryName ?

Correct

[mburumaxwell]

Removal of explicit inputs in favour of the configuration file is still planned though having been pushed ahead since July/August.

In #444, support for multiple repositories (via targetRepositoryName) when using dependabot.yml was added which works by making a HTTP request to Azure DevOps API.

You will still need to add dependabot.yml file to each repository that needs to be updated even though the pipeline is shared.