The HTTP status code for each request is now included in the response metadata.
What does this PR do?
Adds HTTP status code of response
Why is it important/What is the impact to the user?
Adds HTTP status code of response, so that a pipeline can differentiate between the semantics of different error status codes. For example, in some contexts a 404 (Not Found) is substantially different than a 400 (Bad Request), and it may be helpful for downstream plugins in a pipeline to handle the two cases separately.
Checklist
[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have made corresponding change to the default configuration files (and/or docker env variables)
[x] I have added tests that prove my fix is effective or that my feature works
Release notes
The HTTP status code for each request is now included in the response metadata.
What does this PR do?
Adds HTTP status code of response
Why is it important/What is the impact to the user?
Adds HTTP status code of response, so that a pipeline can differentiate between the semantics of different error status codes. For example, in some contexts a
404(Not Found) is substantially different than a400(Bad Request), and it may be helpful for downstream plugins in a pipeline to handle the two cases separately.Checklist
Related issues