Microsoft.Network: `securityRule` resource group name not respecting case sensitivity

[katbyte]

opening as a copy of https://github.com/Azure/azure-rest-api-specs/issues/8309 as it was closed due to not being a rest API spec issue (its a service issue) When creating a securityRule, the case of resource group name is inherited from the networkSecurityGroup ignoring case passed as a parameter.

Repro steps:

Create resource group with resourceGroupName = "test-rg" Create network security group with resourceGroupName = "TEST-RG" Create security rule associated to network security group created in step 2 with resourceGroupName = "test-rg" Subsequent GET of security rule created in step 3 has resourceGroupName with value of "TEST-RG" For example, when creating a virtualNetwork associating a subnet if created with virtualNetwork.resourceGroupName = "test-rg" and subnet.resourceGroupName = "TEST-RG", performing a GET subnet respects case sensitivity of resource group name passed at create time, i.e. GET returns subnet.resourceGroupName = "TEST-RG".

[ghost]

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

[ArcturusZhang]

Hi @katbyte I have tagged this issue therefore the corresponding service team could have a look at this.

[ghost]

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

[rushabh268]

@ArcturusZhang I am seeing this issue as well. Any chance when this can be fixed?

[ghost]

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

[ArcturusZhang]

Hi @rushabh268 sorry for the inconvenience but this has to be fixed on the service side rather than in this SDK. Therefore I have tagged this issue again with the Service Attention label which would send notifications to the corresponding service team and they may have a look at this issue

[ghost]

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

[allegradomel]

@anharazi, can you please take a look? This a service side issue

[ghost]

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

[ghost]

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

[anharazi]

https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/resource-api-reference.md The resource group names and resource names should be matched case insensitively. That means, for example, if a user creates a resource in resource group "rG1", and then calls a read operation on "RG1", the same resource should be returned even though the casing differs. Additionally, the REST API MUST preserve the casing provided by the user. That means the API should return back the most recently specified casing to the client (and API MUST not normalize / return back a toupper/tolower form of the resource group or resource name, for example).

[allegradomel]

#please-close

[tombuildsstuff]

@allegradomel why is this closed? Has this issue been fixed?

[tombuildsstuff]

ping @allegradomel

[tombuildsstuff]

@ArcturusZhang can we re-open this until we can confirm if this has been fixed?

[katbyte]

Hey @allegradomel @jhendrixMSFT @JeffreyRichter - This was closed without a fix or adequate response: Can we please reopen this until it has been resolved?

[ArcturusZhang]

Reopen this issue per request

[rushabh268]

Any update on when this will be resolved?

[github-actions[bot]]

Hi @katbyte, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.