InvalidTemplate with .bicepparam file - expected value of type <something> and received a value of type "Object"

[hooverken]

I'm using a parameters file (.bicepparam) with a basic template and I'm seeing something really weird. I created a minimal test case that triggers the same error for both myself and others. I also checked two most recent releases of Bicep with the same result ( 0.22.6 and 0.21.1).

test.bicep has two lines in it:

param foo int = 100
output out int = foo

test.bicepparam also has two lines in it:

using './test.bicep'
param foo = 404

Important clue: If I use "Generate parameters file" in VS Code and select JSON as the output type, the generated JSON parameters file validates correctly.

Can anyone help me understand why this isn't considered valid?

[SvenAelterman]

I have independently tested this scenario and can confirm this behavior. Bicep 0.22.6.

This seems to be a PowerShell-specific issue. Deploying the same template and param file with az cli 2.53 and az bicep 0.22.6 works.

[johnlokerse]

Yes, this issue is because of Azure PowerShell. I believe it is fixed in Az.Resources v6.11.2: https://github.com/Azure/azure-powershell/releases/tag/Az.Resources-v6.11.2

[SvenAelterman]

Thanks, that looks to be the issue indeed.

Note: I am on Az module version 10.4.1, which presumably doesn't have Az.Resources 6.11.2 yet. I manually updated Az.Resources and it gave me 6.11.2, but running the deployment still fails. Could that be because New-AzSubscriptionDeployment won't use the latest available version of Az.Resources but only the version it was bundled with?

[anthony-c-martin]

I believe New-AzSubscriptionDeployment is part of Az.Resources. Is it possible you have multiple copies installed side by side, and the wrong one is being used? Is there a way to uninstall the older version of Az.Resources?

[SvenAelterman]

You're right. After updating the module, I didn't unload the older version from my PowerShell session. Doing that (and uninstalling the old version, for good measure) fixed it. Thanks!

PS: Handy PowerShell script to uninstall old versions of any module (but it won't remove child modules, use this gist for that instead):

$ModuleName = 'Az.Resources';
$Latest = Get-InstalledModule $ModuleName; 
Get-InstalledModule $ModuleName -AllVersions | ? {$_.Version -ne $Latest.Version} | Uninstall-Module -WhatIf

(Remove the -WhatIf parameter at the end if you're satisfied with the output.)

[hooverken]

Confirmed that the error was cleared by updating modules. Thanks everyone!