az vmss diagnostics set --resource-group <rg> --vmss-name <vmss> --settings router_config.json --protected-settings protected.json gives error The value of parameter type is invalid.
See original GitHub issue
az feedbackauto-generates most of the information requested below, as of CLI version 2.2.0-1
Describe the bug az vmss diagnostics set cli gives error"The value of parameter type is invalid."
To Reproduce Steps to reproduce the behavior. Run the command
- az vmss diagnostics set --resource-group <rg> --vmss-name <vmss> --settings router_config.json --protected-settings protected.json
Expected behavior Enable LinuxDiagnostic on VM scale set
Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build) / CLI version (az --version) / OS version / Shell Type (e.g. bash, cmd.exe, Bash on Windows)
Docker container - VERSION=" Ubuntu 18.04.4 LTS (Bionic Beaver)"
Additional context Add any other context about the problem here.
It used to work on a older version of az cli 2.0.66
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:21 (9 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Looks like Azure CLI version 2.2.0 forgot to pass the extension’s type to the underlying Resource Provider.
eg. with CLI 2.1.0 “extensions”: [ { “name”: “customScript”, “properties”: { “autoUpgradeMinorVersion”: true, “publisher”: “Microsoft.Azure.Extensions”, “type”: “CustomScript”, “typeHandlerVersion”: “2.0”, “settings”: {“commandToExecute”:“echo testing”} }
and with CLI 2.2.0 “extensions”: [ { “name”: “customScript”, “properties”: { “autoUpgradeMinorVersion”: true, “publisher”: “Microsoft.Azure.Extensions”, “typeHandlerVersion”: “2.0”, “settings”: {“commandToExecute”:“echo testing”} }
I have opened a PR to fix this issue. The root cause is that Python SDK abandoned
type. Instead, it usestype1now. I am very confused why there is such kind of change!!!