Azure / Azure/azure-rest-api-specs
[BUG] `Microsoft.Security/locations/jitNetworkAccessPolicies@2020-01-01` returns undefined property "location"
- 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/b3d5c34b3447f71ca8474aa9d32449aafe3996a2/specification/security/resource-manager/Microsoft.Security/stable/2020-01-01/jitNetworkAccessPolicies.json#L434
### API Spec version
2020-01-01
### Describe the bug
In the GET response, the `location` field is returned but not defined in the swagger.
### Expected behavior
In the GET response, the `location` should not be returned, or should be defined in the swagger.
### Actual behavior
In the GET response, the `location` field is returned but not defined in the swagger.
### Reproduction Steps
1. Create the resource.
2. Call GET API and check the response.
### Environment
_No response_
Contributor guide
Research direction
Start with the linked specification file specification/security/resource-manager/Microsoft.Security/stable/2020-01-01/jitNetworkAccessPolicies.json around line 434, then inspect the GET response schema against the reported response. The work is done when the specification accurately reflects the API's location field behavior and the updated spec validates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, openapi
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100