Azure / Azure/azure-rest-api-specs
Media Services API 2020-05-01 returns 400 rather than 404 when a private endpoint connection cannot be found
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 424
Description
Hi there, it appears the Media Services API returns a 400 instead of a 404 when a PrivateEndpointConnection does not exist.
> media.PrivateEndpointConnectionsClient#Get: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="Private endpoint connection name is not valid"
Can this be fixed?
Thanks!
Contributor guide
Research direction
Start by locating the Media Services API 2020-05-01 specification and its PrivateEndpointConnection GET operation. Compare the documented behavior for a missing connection with the reported 400 response. Done means the API behavior or specification clearly represents a missing private endpoint connection as 404, with any applicable validation captured.
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
- Needs clarification
- Newbie friendliness
- 35/100