The HTTP status code of the function being executed and potentially any other useful meta-data should be returned to the X-Callback-Url as a HTTP Header
Current Behaviour
No context about pass/failure, but it appears if the process gives a bad HTTP code we may get an empty body.
Possible Solution
This is not a refactoring exercise, so it shouldn't restructure the code unnecessarily or make unrelated changes.
This should populate a header such as X-Status-Code: 400 or similar.
Steps to Reproduce (for bugs)
Create a classic function that exits with non-zero
Or create a function with of-watchdog that returns non-200
Expected Behaviour
The HTTP status code of the function being executed and potentially any other useful meta-data should be returned to the X-Callback-Url as a HTTP Header
Current Behaviour
No context about pass/failure, but it appears if the process gives a bad HTTP code we may get an empty body.
Possible Solution
This is not a refactoring exercise, so it shouldn't restructure the code unnecessarily or make unrelated changes.
This should populate a header such as
X-Status-Code: 400
or similar.Steps to Reproduce (for bugs)
Context
Confusing user experience for failed executions