An Azure service that automates the access and use of data across clouds without writing code.
Parameterizing managed connectors breaks workflow run history in Logic App Standard?
I have parameterized the configuration for a managed (file system) connector for proper CI/CD and due to the fact that configuration differs depending on the target environment. This is the relevant part from the connections.json:
"managedApiConnections": {
"test-filesystem": {
"api": {
"id": "@appsetting('test_fs_connection_api_id')"
},
"authentication": {
"type": "ManagedServiceIdentity"
},
"connection": {
"id": "@appsetting('test_fs_connection_id')"
},
"connectionRuntimeUrl": "@appsetting('test_fs_connection_runtime_url')"
}
}
As the settings differ from environment to environment, the appropriate values are fetched from application configuration / environment variables using the @appsetting() function. This works fine at runtime. However, when I examine the workflow run history (either stateful or stateless with debugging), I get the following error:
This is from the 'List files in folder' action, but the same issue occurs with any action employing the same connector.
It seems to me that there is a bug in the workflow run history functionality in that it does not properly expand/interpret parametrized values - nor remember the actual value used during the run, but rather fetches the value in the current configuration and expects hard-coded values to have been used there.