In some OpenShift clusters, particularly OpenShift Online Starter, it takes a while for the route to "stabilize" and during that timeframe, the route intermittently succeeds and fails. I'd like to enhance the @AwaitRoute mechanism to support a configurable amount of repetitions -- the route must respond successfully several times in a row to be considered available. Default number of repetitions would be 1, i.e. current behavior.
Expected Behaviour
Be able to specify that the route must respond successfully e.g. 20 times in a row before it's considered available by the @AwaitRoute mechanism.
Current Behaviour
The @AwaitRoute mechanism only waits for the first successful response.
Issue Overview
In some OpenShift clusters, particularly OpenShift Online Starter, it takes a while for the route to "stabilize" and during that timeframe, the route intermittently succeeds and fails. I'd like to enhance the
@AwaitRoutemechanism to support a configurable amount of repetitions -- the route must respond successfully several times in a row to be considered available. Default number of repetitions would be 1, i.e. current behavior.Expected Behaviour
Be able to specify that the route must respond successfully e.g. 20 times in a row before it's considered available by the
@AwaitRoutemechanism.Current Behaviour
The
@AwaitRoutemechanism only waits for the first successful response.Steps To Reproduce
oc logininto an OpenShift Online Starter clustermvn clean verify -Popenshift,openshift-itin a local clone of e.g. https://github.com/openshiftio-vertx-boosters/vertx-http-boosterAdditional Information
I will be submitting an issue report to the OpenShift Online team as well.