Microsoft.Automation/automationAccounts/variables@2022-08-08 - doesn't seem to be sending strings to ARM correctly
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
**Bicep version**
Bicep CLI version 0.12.40 (41892bd0fb)
**Describe the bug**
When trying to use the following resource (https://learn.microsoft.com/en-us/azure/templates/microsoft.automation/automationaccounts/variables?pivots=deployment-language-bicep) I attempt to define the value of the variable, and anytime I define a string I get the following error. **Invalid JSON - Kindly check the value of the variable.**
Below is the bicep example:
```bicep
resource aavar 'Microsoft.Automation/automationAccounts/variables@2022-08-08' = {
name: 'bicep'
parent: autoaccount
properties: {
description: 'test'
isEncrypted: false
value: 'totally a string'
}
}
```
**To Reproduce**
attempt to use Microsoft.Automation/automationAccounts/variables@2022-08-08 and define a variable with a string value.
**Additional context**
Just as an FYI, Integers and Booleans seem to work fine.
Contributor guide
Research direction
Start by reproducing the Microsoft.Automation/automationAccounts/variables@2022-08-08 resource from the Bicep example, comparing its string behavior with the working integer and Boolean values. Check how the Azure resource expects the variable value to be represented; done means a string value deploys successfully without the “Invalid JSON” error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100