Open magodo opened 1 year ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @dnssuppgithub.
Author: | magodo |
---|---|
Assignees: | - |
Labels: | `Network - DNS`, `Service Attention`, `needs-triage` |
Milestone: | - |
Note: this is impacting multiple type of resources in azure related to DNS
When creating a DNS resolver via following request:
PUT https://management.azure.com/subscriptions/xxxx/resourceGroups/acctestRG-ACRTask-211215101546495724/providers/Microsoft.Network/dnsResolvers/ababab?api-version=2022-07-01
After created, I do a GET on the resource and the response returned me:
The expected behavior is that RP team guarantees the round trip consistency and keep the value as what users have specified, i.e. "2023-07-05T13:06:05Z".
This behavior applies not only to the dns resolver, also applies to the dns resolver forwarding ruleset, etc.
Reference
https://github.com/hashicorp/terraform-provider-azurerm/issues/22408