JSON requires escaped double quotes

[mattsmall1972]

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
When passing JSON to CLI, an error occurs:
az : Expecting property name enclosed in double quotes: line 1 column 2 (char 1)

To Reproduce
PS C:\Users\msmall.NORTHAMERICA> az monitor diagnostic-settings create -n "msmall-01"
--resource "/subscriptions//resourceGroups/SME/providers/Microsoft.DocumentDB/databaseAccounts/msmall" --event-hub "msmall"
--event-hub-rule "/subscriptions//resourceGroups/Main/providers/Microsoft.EventHub/namespaces/msmall/AuthorizationRules/RootManageSharedAccessKey" --storage-account "/subscriptions<subscriptionid>/resourceGroups/Main/providers/Microsoft.Storage/storageAccounts/dbvulnerability"
--logs '{"category":"QueryRuntimeStatistics","enabled":"true","retentionPolicy":{"days":"6","enabled":"true"}}'

Expected behavior
Command returns as expected

Environment summary
az --version
azure-cli 2.21.0
core 2.21.0
telemetry 1.0.6
Extensions:
resource-graph 1.0.0
Python (Windows) 3.6.8 (tags/v3.6.8:3c6b436a57, Dec 23 2018, 23:31:17) [MSC v.1916 32 bit (Intel)]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.

Additional context
Issue is resolved by escaping the double quotes in the JSON:
--logs '[{"category":"QueryRuntimeStatistics","enabled":"true","retentionPolicy":{"days":"6","enabled":"true"}}]'

[yonzhan]

monitor

[jiasli]

@mattsmall1972, I believe you are hitting Quoting issues with PowerShell. That's why double quotes need to be escaped again as \" with CMD syntax.

[jiasli]

BTW, your string provided in Additional context is not rendered correctly. Even though you do escape double quotes:

Markdown removes backward slashes in normal text:

So it should be marked as code block to get the raw string displayed:

--logs '[{\"category\":\"QueryRuntimeStatistics\",\"enabled\":\"true\",\"retentionPolicy\":{\"days\":\"6\",\"enabled\":\"true\"}}]'

[mattsmall1972]

@jiasli It appears you are correct that I am running into the known problem. However, is this expected to be fixed or is it by-design?

[jiasli]

@mattsmall1972, I am glad to know it works!

This is a has been a known issue of PowerShell for a long time, but fixing it will actually cause huge breaking changes. It is being traced at PowerShell/PowerShell#1995.

From CLI side, I am adding better error message: #17445.