Description
Is your feature request related to a problem? Please describe.
We are currently using the /ready healthcheck endpoint for our system and are running into issues with the system being marked as 'ready' when the initial data sources have either failed to fetch or have not loaded correctly.
It seems that the current /ready implementation means that regardless of the initial data sources load, as long as there is a successful data-update the system will register as ‘ready’.
Describe the solution you'd like
Have the option to only mark the system as 'ready' if ALL data sources are loaded.
Describe alternatives you've considered
An alternative was suggested via the opal slack channel for a custom policy with rego rules - however we do not want to pursue this route as it will add a maintenance burden to our system.
Additional context
PR planned to make the suggested update