Azure / Azure/azure-rest-api-specs
[BUG]The application security group id in network security group is not being processed as expected
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
### API Spec link
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/network/resource-manager/Microsoft.Network/stable/2024-05-01/networkSecurityGroup.json#L760
### API Spec version
2024-05-01
### Describe the bug
The id format of `sourceApplicationSecurityGroups` and `destinationApplicationSecurityGroups` is changed by the api.
The user's input is ` /subscriptions/xxxxxxxxx/resourceGroups/testRg-Asg/providers/Microsoft.Network/applicationSecurityGroups/testAsg` , however, the api changed the input to all capital case `/subscriptions/481832d6-f3ae-4d03-a6ea-b75760c4f8cc/resourceGroups/TESTRG-ASG/providers/Microsoft.Network/applicationSecurityGroups/TESTASG`
This is obvisiously a bug as the api is not suppose to change any of the user's input
### Expected behavior
The sourceApplicationSecurityGroups and destinationApplicationSecurityGroups id should be whatever I put
### Actual behavior
The id format got changed by the api
### Reproduction Steps
1. send a put request to ["/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/networkSecurityGroups/{networkSecurityGroupName}"](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/network/resource-manager/Microsoft.Network/stable/2024-05-01/networkSecurityGroup.json#L37) , include the sourceApplicationSecurityGroups and destinationApplicationSecurityGroups
2. Get the network security group using the GET request, there will be the difference I mentioned.
### Environment
_No response_
Contributor guide
Research direction
Start with the networkSecurityGroup.json definition for sourceApplicationSecurityGroups and destinationApplicationSecurityGroups, especially the 2024-05-01 PUT and GET operations linked in the issue. Reproduce the request and compare the submitted IDs with the returned values, then determine whether the specification identifies a change needed in this repository. Done means the expected preservation of the application security group IDs is addressed or the service ownership is clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, openapi
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100