Closed ChristopherGLewis closed 2 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @armleads-azure.
Author: | ChristopherGLewis |
---|---|
Assignees: | - |
Labels: | `Service Attention`, `question`, `ARM - Core`, `customer-reported`, `needs-triage` |
Milestone: | - |
I can confirm, also ran in this issue, tag: DeploymentID became : deploymentID
I can confirm the same behavior. In my case I noticed this when using New-AzResourceGroupDeployment version 4.3.1 to deploy the IaaSAntimalware VM extension. I send in the settings as a parameter. Command I used:
New-AzResourceGroupDeployment `
-ResourceGroupName vmrg `
-Name vmextension `
-TemplateFile ./vmextension.json `
-TemplateParameterFile ./vmextension.parameters.json
In vmextension.parameters.json I send in:
{
"AntimalwareEnabled": true,
"RealtimeProtectionEnabled": true,
"ScheduledScanSettings": {
"isEnabled": true,
"day": 7,
"time": 120,
"scanType": "Quick"
}
}
I received the error: VM has reported a failure when processing extension 'IaaSAntimalware'. Error message: "The configuration file does not specify an AntimalwareEnabled value of true (case sensitive).
Then I see the deployment properties from the command and I clearly see that case has changed to lowercase for first character of all input parameter values:
{
"antimalwareEnabled": true,
"realtimeProtectionEnabled": true,
"scheduledScanSettings": {
"isEnabled": true,
"day": 7,
"time": 120,
"scanType": "Quick"
}
}
When I use Azure CLI version 2.24.2 (and version 2.28.0) to deploy the template the deployment is successful:
az deployment group create --resource-group vmrg --name vmextension --template-file ./vmextension.json --parameters ./vmextension.parameters.json
Hi @ChristopherGLewis , this issue has been fixed in Az.Resources>=4.4.0. I saw you were using Az.Resources 4.3.1. Could you please upgrade your Az.Resources and have a try?
Yes, confirmed to be fixed
On Mon, Dec 13, 2021 at 2:39 AM Beisi Zhou @.***> wrote:
Hi @ChristopherGLewis https://github.com/ChristopherGLewis , this issue has been fixed in Az.Resources>=4.4.0. I saw you were using Az.Resources 4.3.1. Could you please upgrade your Az.Resources and have a try?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Azure/azure-powershell/issues/15876#issuecomment-992229553, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACA4VCSNGHNE323GD2A2HOTUQWWKNANCNFSM5EAQDEUA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
-- Christopher G. Lewis http://www.ChristopherLewis.com http://www.christopherlewis.com/
Going to close this issue. Please feel free to open if have any further question.
Description
Tags passed as parameters to New-AzDeployment and New-AzResourceGroupDeployment deployment have their initial character case change
Tag case gets changed in those two commandlets
Steps to reproduce
Bicep file:
ARM:
Parameter file
Environment data
Module versions
Debug output
Error output