Azure / Azure/azure-rest-api-specs
AzureMonitorPrivateLinkScopedResource.Get API returned the incorrect format for the linkedResourceId property
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
After tested, I found [AzureMonitorPrivateLinkScopedResource.Get](https://github.com/Azure/azure-rest-api-specs/blob/407845d6d73536b216cd2fe1bc8d98a4f6935a55/specification/monitor/resource-manager/Microsoft.Insights/preview/2021-07-01-preview/privateLinkScopes_API.json#L636) API returned the value of the linkedResourceId property with incorrect format. It should be like below sample. Seems it's an API bug. Please take a look and fix this issue. Thanks.
Incorrect format for the value of the linkedResourceId property returned by API:
```
{
......
"properties": {
"linkedResourceId": "/subscriptions/xx-xxx-xxx-xxx/resourcegroups/acctestrg-pls-test01/providers/microsoft.insights/components/acctestappinsights-test02"
}
......
}
```
Correct format for the value of the linkedResourceId property returned by API:
```
{
......
"properties": {
"linkedResourceId": "/subscriptions/xx-xx-xx-xx/resourceGroups/acctestRG-pls-test01/providers/Microsoft.Insights/components/acctestAppInsights-test02"
}
......
}
```
Contributor guide
Research direction
Start by reviewing specification/monitor/resource-manager/Microsoft.Insights/preview/2021-07-01-preview/privateLinkScopes_API.json at the AzureMonitorPrivateLinkScopedResource.Get definition around line 636. Compare the linkedResourceId description and schema with the two response examples, then determine whether the specification can represent the required casing; done means the API contract and returned format agree.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, openapi
- Domain
- api, cloud, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100