Handle log responses as text #7776
Merged
Conversation
This file contains 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
Log endpoint always responds as `Content-Type: text/plain` but empty responses are converted to empty objects in JsonApi. In case of resolved non-string log response, consider it empty (string). Signed-off-by: Sami Tiilikainen <97873007+samitiilikainen@users.noreply.github.com>
samitiilikainen
requested review from
Iku-turso and
gabriel-mirantis
and removed request for
a team
Nokel81
approved these changes
May 25, 2023
Merged
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.
Logs are handled as string and log endpoint always responds as
Content-Type: text/plainbut empty responses are converted to empty objects in JsonApi.In case of resolved non-string log response, consider it empty (string).
Fixes error:
