You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Since PR 4091 #4091 the Outputs support the @description('my description') decorator. If you build a bicep file with that, it creates the "metadata": {"description": "value"} in the json file. But if you go the other way round and decompile the json file, which has the metadata declared for an output, it does not create the @description in the bicep file.
To Reproduce
1.) create json with an output, like:
"outputs": {
"virtualMachinesResourceGroup": {
"type": "string",
"value": "[resourceGroup().name]",
"metadata": {
"description": "The name of the Resource Group the VM(s) was/were created in."
}
}
}
2.) run bicep decompile xxx.json
3.) look at the created bicep file in the output section, there is the output but no description on it
The text was updated successfully, but these errors were encountered:
Bicep version
Bicep CLI version 0.4.613 (d826ce8)
Describe the bug
Since PR 4091 #4091 the Outputs support the @description('my description') decorator. If you build a bicep file with that, it creates the "metadata": {"description": "value"} in the json file. But if you go the other way round and decompile the json file, which has the metadata declared for an output, it does not create the @description in the bicep file.
To Reproduce
1.) create json with an output, like:
2.) run bicep decompile xxx.json
3.) look at the created bicep file in the output section, there is the output but no description on it
The text was updated successfully, but these errors were encountered: