az cdn endpoint rule add does not parse match-values correctly

This is autogenerated. Please review and update as needed.

Describe the bug

Command Name az cdn endpoint rule add

Errors:

(BadRequest) Rules validation failed. More information: Value {} is not a valid IP Address in rule iprestriction.
Code: BadRequest
Message: Rules validation failed. More information: Value {} is not a valid IP Address in rule iprestriction.

To Reproduce:

Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

• Create a CDN profile and endpoint. I am using Premium Verizon.
• az cdn endpoint rule add -g {} -n {} --profile-name {} --order 1 --rule-name iprestriction --match-variable RemoteAddress --operator IPMatch --negate-condition true --match-values 1.2.3.4/32,5.6.7.8/32 --action-name UrlRedirect --redirect-type PermanentRedirect --custom-path /403 --debug

Expected Behavior

Where the parameter passed to match-values is a comma separated list of IP addresses in CIDR notation, multiple values should be added to the rule’s match values (docs).

For example --match-values 1.2.3.4/32,5.6.7.8/32 should produce a rule that matches those two IP addresses.

Looking at the debug output, the request seems to combine the two IP addresses into a single, invalid string like

“matchValues”: [“1.2.3.4/32,5.6.7.8/32”]

Environment Summary

Linux-4.19.104-microsoft-standard-x86_64-with-debian-buster-sid, Ubuntu 18.04.4 LTS
Python 3.6.10
Installer: DEB

azure-cli 2.33.1

Extensions:
azure-iot 0.13.0

Dependencies:
msal 1.16.0
azure-mgmt-resource 20.0.0

Additional Context

[t-bzhan]

@chris-hibberd, CLI’s collection property like --match-values use the space as the separator. You command should go like:

az cdn endpoint rule add -g bzhan-poc -n cachekeytest --profile-name msft-test --order 1 --rule-name iprestriction --match-variable RemoteAddress --operator IPMatch --negate-condition true --match-values 1.2.3.4/32 5.6.7.8/32 --action-name UrlRedirect --redirect-type PermanentRedirect --custom-path /403 --debug

The commands works as expected per my test:

[SaurabhSharma-MSFT]

@yonzhan I could see some different error however I could see that IP addresses are passed as single string and thus redirecting this to services team.