Azure / Azure/azure-rest-api-specs
`OperationalInsights@2022-10-01` - `EnableLogAccessUsingOnlyResourcePermissions` can't be set on first time `Workspaces_CreateOrUpdate`
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
we called [`Workspaces_CreateOrUpdate`](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/operationalinsights/resource-manager/Microsoft.OperationalInsights/stable/2022-10-01/Workspaces.json#L128) with [`enableLogAccessUsingOnlyResourcePermissions`](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/operationalinsights/resource-manager/Microsoft.OperationalInsights/stable/2022-10-01/Workspaces.json#L604) = `false` to create **new** workspace, but then it returned `true` in following [`Workspaces_Get`](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/operationalinsights/resource-manager/Microsoft.OperationalInsights/stable/2022-10-01/Workspaces.json#L238).
We have found that it needs an additional call on `Workspaces_CreateOrUpdate` to set `enableLogAccessUsingOnlyResourcePermissions` to correct value.
Contributor guide
Research direction
Start by reading specification/operationalinsights/resource-manager/Microsoft.OperationalInsights/stable/2022-10-01/Workspaces.json, especially Workspaces_CreateOrUpdate, Workspaces_Get, and the enableLogAccessUsingOnlyResourcePermissions definition. Compare the documented create behavior with the reported first-create response and determine what specification change is needed; done means the contract accurately reflects the supported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100