AZL

[tallywizu]

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

Related command

az portal dashboard update

https://docs.microsoft.com/en-us/cli/azure/portal/dashboard?view=azure-cli-latest

Describe the bug
The AZ portal dashboard update command only accepts files with specific encoding which is not mentioned in the Microsoft documentation and throwing up errors when running other encoding types , the encoding type that is accepted is UTF-8

To Reproduce

I converted the file the customer sent to UTF-8 and ran the command but I didn't get any error

I converted the file the customer sent to ucs-2 le bom and I was getting the below error

I took a json file from my lab and converted to ucs-2 le bom but I got the below

Expected behavior

The AZ dashboard update command is suppose to accept any file format and if there any specifics, it should be stated in the Microsoft documentation

Environment summary

Additional context

[yonzhan]

portal

[jsntcy]

@tallywizu, please share the json file that you used so that we can troubleshoot.

You should construct the json file following the format in https://github.com/Azure/azure-cli-extensions/blob/main/src/portal/azext_portal/tests/latest/properties.json

[temidayo0301]

Hello @jsntcy

Please find attached as requested. Thank you.
test.txt

[jsntcy]

@tallywizu, @temidayo0301, I used the file you provided above, but cannot reproduce the issue (I can run the command az portal dashboard update with your json file successfully.), could you please provide more details?

[RomanDvorsky]

Hi, what is the operation system on your machine which you use to reproduce the error? Is it the windows or linux (mac) machine? Are you sure you do try file with windows encoding to get a failure?

[jsntcy]

I use Windows and ran the command with the file @temidayo0301 provided above. What do you mean for "try file with windows encoding to get a failure"?

[RomanDvorsky]

well the cli command works only with utf-8 encoding with CR line end other encoding like with cr lf line end did produce an error.