Closed adamdecaf closed 2 years ago
When we manually trigger shards it would be helpful to return the result of each shard in the response. An example is below.
{ "shards": { "testing": "skipped", "prod": "completed", "uat": "errored" } }
The possible values at first could be skipped, errored and completed. The skipped comes into play when we trigger only some of the shards.
skipped
errored
completed
We've ran into some issues in the real world where /trigger-cutoff isn't fully applied to every instance properly to maintain consistent state.
/trigger-cutoff
FYI this does break the error response, but I'm not aware of anyone using that.
When we manually trigger shards it would be helpful to return the result of each shard in the response. An example is below.
The possible values at first could be
skipped
,errored
andcompleted
. Theskipped
comes into play when we trigger only some of the shards.We've ran into some issues in the real world where
/trigger-cutoff
isn't fully applied to every instance properly to maintain consistent state.