openai / openai/openai-openapi
Validation when using spec in Azure API Management
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.5k
- Forks
- 527
- Avg merge
- 1h 46m
- Merged PRs (30d)
- 2
Description
Hello.
While trying to create a clone of the API in Azure API Management using the version on master, I am getting validation errors of the file.
https://raw.githubusercontent.com/openai/openai-openapi/refs/heads/master/openapi.yaml
This doesn't happen when the version used to create the API is the latest release, which of course is very outdated and therefore I would like to use a more recent version instead.
Thanks a lot for the hard work maintaining this code!
Contributor guide
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 master openapi.yaml linked in the issue and reproduce its import in Azure API Management, then compare it with the latest release version that imports successfully. Done means the current specification can be used to create or clone the API without the reported validation errors.
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