Skip to content

Conversation

@mmyyrroonn
Copy link
Contributor

@mmyyrroonn mmyyrroonn commented Mar 25, 2020

Description of PR (Mandatory)
Fix #11901 #11900 #2092

Now, if user provides --if-none-match, only the empty record-set would be created. The following command would fail by design. It won't bring any breaking change for existing users.

Testing Guide
(Example commands with explanations)

History Notes:
(Fill in the following template if multiple notes are needed, otherwise PR title will be used for history note.)

[Component Name 1] (BREAKING CHANGE:) (az command:) make some customer-facing change.
[Component Name 2] (BREAKING CHANGE:) (az command:) make some customer-facing change.


This checklist is used to make sure that common guidelines for a pull request are followed.

@mmyyrroonn mmyyrroonn merged commit 280bec7 into Azure:dev Mar 27, 2020
@mmyyrroonn mmyyrroonn deleted the fix-11901-support-confirmation-to-create-a-new-record-set branch March 27, 2020 06:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

support new feature in dns add/remove

2 participants