az network private-dns record-set is not idempotent from CLI version 2.37.0

[WGK864]

This is related to #10467.

Related command
az network private-dns record-set

Describe the bug
CLI version 2.36.0 runs this command in an idempotent way. If the record is to be duplicated, it acts as a No-op and returns code 0. In version 2.37.0 this command is no longer idempotent and logs a BadRequest.

To Reproduce
Run az network private-dns record-set in version 2.36.0 and 2.37.0 and notice the different results.

Expected behavior
I expect this command to be idempotent when adding a record that may already exist.

Environment summary
Ran in pipeline worker with ubuntu 20.04 image

[yonzhan]

network

[WGK864]

What is returned (for reference):

ERROR: (BadRequest) The list of record sets of type 'A' may not contain multiple entries with the same 'ipv4Address'.
Code: BadRequest
Message: The list of record sets of type 'A' may not contain multiple entries with the same 'ipv4Address'.

[alanj1998]

@yonzhan Is this something that is/will be worked on?

[necusjz]

@alanj1998, actually, there is no any changes between Azure CLI 2.36.0 and 2.37.0 for this functionality. It should be a change from service side, let's involve service team for help.

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @aznetsuppgithub.

Issue Details

---

This is related to #10467.

Related command
az network private-dns record-set

Describe the bug
CLI version 2.36.0 runs this command in an idempotent way. If the record is to be duplicated, it acts as a No-op and returns code 0. In version 2.37.0 this command is no longer idempotent and logs a BadRequest.

To Reproduce
Run az network private-dns record-set in version 2.36.0 and 2.37.0 and notice the different results.

Expected behavior
I expect this command to be idempotent when adding a record that may already exist.

Environment summary
Ran in pipeline worker with ubuntu 20.04 image

Author:	WGK864
Assignees:	necusjz
Labels:	Network, Service Attention, customer-reported, Auto-Assign
Milestone:	Backlog

[WGK864]

Hey is there any update on this?

[WGK864]

Bump :)

[necusjz]

@rajitaaa Could you please help us explain this behavior? Thanks.