microsoftgraph / microsoftgraph/msgraph-metadata
Invalid path `/admin/serviceAnnouncement/healthOverviews/{serviceHealth-id}/issues`
Nobody has claimed this yet.
- Dominant language
- XSLT
- Stars
- 166
- Forks
- 55
- Avg merge
- 16h 12m
- Merged PRs (30d)
- 14
Description
Open API specification contains description of /admin/serviceAnnouncement/healthOverviews/{serviceHealth-id}/issues endpoint
'/admin/serviceAnnouncement/healthOverviews/{serviceHealth-id}/issues':
description: Provides operations to manage the issues property of the microsoft.graph.serviceHealth entity.
get:
...
post:
...
parameters:
- name: serviceHealth-id
in: path
description: The unique identifier of serviceHealth
required: true
schema:
type: string
x-ms-docs-key-type: serviceHealth
But request GET /admin/serviceAnnouncement/healthOverviews/{serviceHealth-id}/issues fails with 404
{
"error": {
"code": "UnknownError",
"message": "",
"innerError": {
"date": "2023-09-20T12:32:06",
"request-id": "2aeda9ef-547f-4caf-93a2-979c53c72c31",
"client-request-id": "a4a3c3ae-1b08-8ce5-40d0-a9425c5edb52"
}
}
}
In fact, issues can be accessed only by calling
GET /admin/serviceAnnouncement/issues
Also post operation doesn't make sense, because service health is 'read-only' endpoint
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Open API specification entry for /admin/serviceAnnouncement/healthOverviews/{serviceHealth-id}/issues and compare it with the working /admin/serviceAnnouncement/issues endpoint described in the issue. Verify the service-health resource is read-only and confirm the specification no longer advertises an invalid nested GET or POST operation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100