-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DNS] DNS record management commands should support --if-match #2092
Comments
jtuliani
changed the title
[DNS] DNS record management commands should support if-match and if-none-match
[DNS] DNS record management commands should support --if-match
Feb 16, 2017
tjprescott
added
Network - DNS
az network dns
and removed
Network
az network vnet/lb/nic/dns/etc...
labels
Nov 29, 2018
@myronfanqiu add to S162. |
This was referenced Jan 19, 2020
Thank you! |
@jtuliani Hello. Thanks for feedback. Do you still remember your original thoughts? I want to double confirm, do you want an extra argument |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The commands under 'az network dns record ...' are used to add/remove records from DNS record sets. They can also create a new record set if one does not already exist.
These operations need to support optimistic concurrency to protect against concurrent changes.
To address this, the '--if-match ' parameter should be supported on both the 'add' and 'remove' commands (and 'update-soa').
When the record set doesn't already exist and thus a new record set is being created, the command should always include '--if-none-match *' to protect against concurrent operations. This this should always be applied in this case, there is no need to expose it in the command parameters.
The text was updated successfully, but these errors were encountered: