Azure / Azure/azure-cli

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

Open
#22,886 8 comments 1 reaction 1 assignee Claimed by @necusjz View on GitHub
act-quality-productivity-squad Auto-Assign customer-reported Network Service Attention
Dominant language
Python
Stars
4.6k
Forks
3.5k
Avg merge
3d 2h
Merged PRs (30d)
60

Description

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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.