[DNS] Issues with 'az network dns record-set update'

[jtuliani]

Issues with 'az network dns record-set update':

• 1. As with zone update, the command should support update operations only. The 'if-none-match' property should therefore not be exposed. (should be removed from Swagger/SDK if N/A)
• 2. As with zone update, the two command groups under '--help' both named 'Generic Update Arguments' should be merged. (PR [Help] Fix argument group ordering. #1015)
• 3. Again under '--help' there needs to be a description. Also under 'az network dns record-set -h' (PR [Network] DNS Record Set Create Updates #1583)
• 4. --zone-name and --type should accept short form (-z and -t) (PR [Network] DNS Record Set Create Updates #1583)
• 5. No way to update metadata on record sets (PR [Network] DNS Fixes Round 2 #1592)
• 6. Completely unclear how --add / --remove / --set should be used. And given the separate commands for adding and removing records, even the presence of these commands is very confusing indeed. Is there any way these commands can be used to add/remove/update records? Tracked more generally in Generic Update Needs Better Documentation #1582

[JasonRShaver]

• remove if-none-match
• add short summary
• add examples section
• add -z and -t

Discuss generic update and arugments section
Discuss adding metadata with --add

[jtuliani]

For metadata, we need examples covering:

• Removing all metadata
• Adding a new metadata item (suggest using "dept=finance")
• Removing an existing metadata item, leaving other items in place (again, use "dept=finance")

[tjprescott]

@jtuliani IRT item 1, the DNS SDK is unique in that it actually has a patch operation for a pure update (although we leverage create_or_update for other reasons), but even that exposes if_none_match.