-
Type:
Sub-task
-
Resolution: Won't Do
-
Priority:
L3 - Default
-
Affects Version/s: None
-
Component/s: backend
-
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