Use different connection when running Azure Logic App workflow locally

Question

I have a question about Azure Logic Apps (Standard) local development. I'm triggering a workflow from a storage queue. Inside Azure the connection uses a ManagedServiceIdentity. This option is not locally available however. Locally I can use a connection string with value "UseDevelopmentStorage=true".

However, the structure of the connection inside the connections.json is different between the managed identity and connection string types. So changing a simple app setting in the local.settings.json doesn't work.

Connection example with managed identity:

"app-storage-queue-connection": {
  "parameterValues": {
    "connectionString": "@appsetting('app-storage-queue-endpoint')"
  },
  "parameterSetName": "connectionString",
  ...
}

Connection example with connection string:

"app-storage-queue-connection": {
    "parameterValues": {
        "authProvider": {
            "Type": "ManagedServiceIdentity"
        },
        "queueServiceUri": "@appsetting('app-storage-queue-endpoint')"
    },
    ...
}

Is there a way to create a 'local.connections.json' file similar to the 'local.settings.json' file? Or to solve this issue another way?

I tried creating a local.connections.json, but it doesn't work.

A workaround would be to configure the connections.json with the local 'connection string' connection. Create a 'remote.connections.json' with the managed identity connection and use that during deployment from my Azure Pipeline. But I'm hoping there is a more elegant way.