We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Description of the issue
When a bool is converted to a string the default .NET type converter has a different behaviour than ARM.
For example:
string(true())
True
string(false())
False
true
false
To Reproduce
Steps to reproduce the issue:
{ "$schema": "https://schema.management.azure.com/schemas/2019-08-01/tenantDeploymentTemplate.json#", "contentVersion": "1.0.0.0", "variables": { "lookup": { "True": { "value": "True" }, "true": { "value": "true" }, "false": { "value": "false" } } }, "resources": [ { "type": "Namespace/resourceType", "apiVersion": "2020-05-01", "name": "resource", "location": "region", "properties": { "value1": "[variables('lookup')[string(empty(''))].value]", "value2": "[variables('lookup')[tolower(string(empty('')))].value]", "value3": "[variables('lookup')[string(not(empty('')))].value]" } } ] }
Expected behaviour
Update string() function to use True and False for converted bool value instead of true and false.
string()
Module in use and version:
Captured output from $PSVersionTable:
$PSVersionTable
Name Value ---- ----- PSVersion 7.1.3 PSEdition Core GitCommitId 7.1.3 OS Microsoft Windows 10.0.19043 Platform Win32NT PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…} PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 WSManStackVersion 3.0
The text was updated successfully, but these errors were encountered:
Fix case and bool parsing issues Azure#793 Azure#794
7bbe793
Fix case and bool parsing issues #793 #794 (#795)
759fa9f
BernieWhite
Successfully merging a pull request may close this issue.
Description of the issue
When a bool is converted to a string the default .NET type converter has a different behaviour than ARM.
For example:
string(true())
=True
,string(false())
=False
true
=true
,false
=false
.To Reproduce
Steps to reproduce the issue:
Expected behaviour
Update
string()
function to useTrue
andFalse
for converted bool value instead oftrue
andfalse
.Module in use and version:
Captured output from
$PSVersionTable
:The text was updated successfully, but these errors were encountered: