Details
-
Sub-task
-
Status: Done
-
L3 - Default
-
Resolution: Won't Do
-
None
-
Not defined
Description
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