Support bundle download endpoints could distinguish success and failure status codes in OpenAPI#7346
Draft
Support bundle download endpoints could distinguish success and failure status codes in OpenAPI#7346
Conversation
…re status codes in OpenAPI
Collaborator
|
I think this is the right approach for all support bundle endpoints - I either forgot or never knew about I'll give a shot at updating all these response endpoints in #7187 to confirm this works with the integration tests |
Collaborator
|
Following up on comments made in chat:
|
Contributor
Author
|
Yeah. I don't think we can do this right now, but ideally we'd like the following to appear in the OpenAPI document:
|
This was referenced Jan 15, 2025
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
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.
this is probably wrong; we might return a 200 or 206.