-
Sub-task
-
Resolution: Won't Do
-
L3 - Default
-
None
-
Not defined
We currently have some jobs which wait for Optimize to be ready by using the status endpoint before doing a certain action. We should use the dedicated readiness endpoint for this instead.
ATs:
- CI jobs use the readiness endpoint to check availability of Optimize rather than the status endpoint
I had a look through all our usages of the status endpoint and they are actually all quite valid. You could argue that we should move the release job check at the end to use the new health endpoint, but on balance I don't think it would be an improvement, as failing to be ready shouldn't fail the whole build in the same way that failing an api response should