Replacing properties: allow wildcards in the PATH column of the configuration file (CSV)

[marco-piazzi]

It would be great if the PATH column of the configuration file (CSV) could accept wildcards in order to make it easier to replace of multiple properties.
Let's assume we have an ADF pipeline with many web activities. Each of these activities uses an Integration Runtime that needs to be replaced in different environments.
A simplification of this scenario is represented by the following JSON snippet:

{
"name": "Contoso_MyPipeline",
  "properties": {
    "activities": [
      {
        "name": "Web_MyActivity1",
        "type": "WebActivity",
        "typeProperties": {
          "connectVia": {
            "referenceName": "my-shir-dev-01",
            "type": "IntegrationRuntimeReference"
          }
        }
      },
      {
        "name": "Web_MyActivity2",
        "type": "WebActivity",
        "typeProperties": {
          "connectVia": {
            "referenceName": "my-shir-dev-01",
            "type": "IntegrationRuntimeReference"
          }
        }
      }
    ]
  },
  "type": "Microsoft.DataFactory/factories/pipelines"
}

The generic rule to catch all web activities in all pipelines that start with "Contoso_" and replace the Integration Runtime reference should be:

type,name,path,value
pipeline,Contoso_*,activities[Web_*].typeProperties.connectVia.referenceName,"$Env:INTEGRATIONRUNTIMENAME"

The NAME column already supports wildcards. It would be great if the path column supported them too.

Thank you for the incredible effort you are putting into this awesome tool!
Marco