Closed gdmarsh closed 2 years ago
oh that is a good catch @gdmarsh :)
The way the healthcheck policy healthy rule works, it checks both the success of at least one update made by both policy updater and data updater - since data updater is off - no data updates are ever made.
It's a super easy fix - will get to it this weekend :)
I was looking at running the healthcheck policy as it is useful configuring this for a Kubernetes environment but there is also no requirement currently to update data, only policy. It turns out that by disabling data updates using the
OPAL_DATA_UPDATER_ENABLED
option it causes the healthcheck to never return true.Steps to reproduce
docker-compose-with-callbacks.yml
to disable data updates (gdmarsh/opal@44e6db9)v1/data/system/opal
to show that ready and healthy both return false and will never end up being true