-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Private DNS RecordSet: ResourceGroup name has wrong case #6641
Comments
@shahabhijeet any update on when this'll be fixed? |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @aznetsuppgithub. |
This is expected behavior. ARM resource names are not case sensitive and application code must not rely on the case of the resourcename or resource group name. |
@rohinkoul unfortunately other ARM API's can be case sensitive, meaning that unless every API and every client treat all URI's as case insensitive (which they don't), then by definition every client has to treat these as case sensitive. It's worth mentioning that both RFC 2616 and RFC 7230 define that both URI's and Components should be treated as case-sensitive by clients - so I believe this wants fixing to match the industry best practice here? Thanks! |
Please refer : https://docs.microsoft.com/en-us/rest/api/resources/resources/update resourceGroupName path True Regex pattern: ^[-\w._()]+$ ARM Resource Group Name in ARM URI is case insensitive. If you have noticed an Azure Service not abiding with this please let us know. |
@lilyjma Please close this as won't fix. As mentioned above resourceGroup names are not case sensitive. |
@rohinkoul the HTTP Specification - namely RFC7230, section 2.7.3 (and indirectly RFC 2616) state that:
Ultimately whilst a service itself may opt to be case-insensitive for Request URI's - per the HTTP Specification, references to URI's (e.g. in Responses) should be case-sensitive. As such I believe this bug is valid and should remain open until this API complies with the HTTP Specification? Thanks! |
@rohinkoul for reference here's a link to the Azure API Documentation where it's clarified this is a bug in the API:
As such - is there a timeframe for when these casing bugs will be fixed? Thanks! |
It's worth noting this also appears to affect the Virtual Network Peering API's: hashicorp/terraform-provider-azurerm#8289 |
@karravi-msft could you take a look and if necessary add this to our backlog. |
Hi @rohinkoul @karravi-msft Any update on this? It has been years since last update. |
While working on a new terraform resource for a private DNS Zone A record ( hashicorp/terraform-provider-azurerm#3849 ) I stumbled across an issue with upper case resource group names.
Step to reproduce:
tesT
The API response for the A record resource is like:
The problem is the lower case in the
id
attribute for the resource grouptest
Expected Behaviour:
Having an id with resource group name
tesT
.This is the behaviour when creating a recordset for the normal DNS zones.
The text was updated successfully, but these errors were encountered: