RANGER-5630:Swagger UI requests non-existent swagger.json instead of generated openapi.json#998
Merged
Merged
Conversation
…generated openapi.json
dhavaljrajpara
requested review from
dhavaljrajpara,
dineshkumar-yadav,
fimugdha and
pradeepagrawal8184
dhavaljrajpara
approved these changes
Jun 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR fixes the Swagger UI API documentation page failing to load due to an incorrect reference to
swagger.json. The UI has been updated to loadopenapi.json, which is the API specification file generated and packaged by the Ranger build process.How was this patch tested?
/apidocs/swagger.html.openapi.jsonis loaded successfully (HTTP 200).