Describe the problem to be solved
It would be very cool if there is a way to make the configurable webhook URL return a different HTTP status code at a given percentage to mimic real life scenarios. So, if I set it to 50%, then the possibility is 50% on each request that it throws the alternative HTTP status code.
Maybe also some general response behavior based on time or a series of requests, such as:
- returning HTTP 429 after too many requests, recovering after the retry-after header time is expired
- returning HTTP 410 indefinitely after a set time or number of requests, as per CloudEvents webhook spec
Suggest a solution
No response
Additional context
No response
Describe the problem to be solved
It would be very cool if there is a way to make the configurable webhook URL return a different HTTP status code at a given percentage to mimic real life scenarios. So, if I set it to 50%, then the possibility is 50% on each request that it throws the alternative HTTP status code.
Maybe also some general response behavior based on time or a series of requests, such as:
Suggest a solution
No response
Additional context
No response