You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of these requests when being invoked will start failing because of the invalid string key. Then the user would have to manually kill all ingested invocations
Independently from the context of the PR, this comment here #815 (comment) makes me wonder whether we should have a way to kill/cancel a range of invocations.
This could be useful in general in many situations where the user deployed a bad service, or many requests were received with wrong payload due to a misconfiguration/bad contract.
The text was updated successfully, but these errors were encountered:
This could be a useful admin command, indeed. What is a bit unclear to me is how much control would a user want to have over the range/set (full range/set vs. partial range/set).
This feature can probably be implemented driven by demand from our users.
What is a bit unclear to me is how much control would a user want to have over the range/set (full range/set vs. partial range/set).
Same. Perhaps some simple strategies that can be useful for development are "kill all invocations to this service" or even better "to this service instance" (for keyed services).
Independently from the context of the PR, this comment here #815 (comment) makes me wonder whether we should have a way to kill/cancel a range of invocations.
This could be useful in general in many situations where the user deployed a bad service, or many requests were received with wrong payload due to a misconfiguration/bad contract.
The text was updated successfully, but these errors were encountered: