Connection Support for Parameters.json

[ChristinaHebertHCS]

I am finding when I run my unit tests it errors on the connections.json file because its linking to a parameters.json file instead of the appsettings.

I am wanting to confirm if the code supports both? I had to do a work around in updating the connections.json to instead use appsettings and replace the authentication with the value from the parameters file. (connections.json is the original file and connections-unittest.json is the rewrite).

I have found when attempting to run the Logic Apps with the updated connections.json it doesn't work live anymore with the rewrite. To be able to test I have to rename the connections-unittest.json to connections.json and then back again once I am done testing. I am wondering if the library could be updated to support both?

connections-unittest.json
connections.json
parameters.json

[mark-abrams]

Hi @ChristinaHebertHCS . Yes, you are right, the framework only supports connection runtime URLs that are inline in the connectionRuntimeUrl attribute in the connections.json file, or parameterised using @appSetting(). It does not support parameterisation using @parameters().

When I wrote this part of the framework, the Standard Logic App extension wasn't using @parameters() to parameterise the connections runtime URLs, so the framework code worked. But now the extension uses @parameters(), hence your observation.

I'll add this to the backlog for the next version.

[mark-abrams]

This will be fixed in the next version of LogicAppUnit, version 1.11.0.

[mark-abrams]

@ChristinaHebertHCS , version 1.11.0 has been released to NuGet that fixes this issue.