Regression in Publish-AzBicepModule 6.11.1 -> 6.11.2

[StephenWeatherford]

With Az.Resources 6.11.1:

PS C:\Users\<>\repos\template-examples\bicep\modules\simpleModule> Publish-AzBicepModule -FilePath main.bicep -Target br:sawbicep.azurecr.io/demo/testps:v10 -verbose
VERBOSE: Using Bicep v0.23.1
Publish-AzBicepModule:
PS C:\Users\<>\repos\template-examples\bicep\modules\simpleModule>

with 6.11.2:

PS C:\Users\<>\repos\template-examples\bicep\modules\simpleModule> Publish-AzBicepModule -FilePath main.bicep -Target br:sawbicep.azurecr.io/demo/testps:v11 -verbose
VERBOSE: Using Bicep v0.23.1
VERBOSE: Calling Bicep with arguments: publish "C:\Users\<>\repos\template-examples\bicep\modules\simpleModule\main.bicep" --target 'br:sawbicep.azurecr.io/demo/testps:v11'
VERBOSE:
Publish-AzBicepModule: The specified module reference scheme "'br" is not recognized. Specify a path to a local module file or a module reference using one of the following schemes: "br", "ts"
PS C:\Users\<>\repos\template-examples\bicep\modules\simpleModule>

NOTE: Calling bicep directly with the arguments that it says it's using for bicep actually does work in pwsh (Mac and Windows), but gives the scheme error on command line for Windows but works on Mac terminal. Which is weird, because I get the same scheme error from Publish-AzBicepModule on Mac and Windows.

[StephenWeatherford]

@anthony-c-martin Most likely caused by f3f66fd1b2 ("Support supplemental parameters when used with .bicepparam parameter file (#22904)", 2023-10-11)

[anthony-c-martin]

Agreed, that sounds highly likely - I made a significant change to the way that arguments were passed to the Bicep binary.

[StephenWeatherford]

Fix merged in Azure PowerShell: Azure/azure-powershell#23403. I assume it will go out with the next release, which I believe is in December.