This message was deleted.

Hi @Philip Claesson! Quite a mystery. Can you share the logs for the server and the client ? Might have clues to debug. Also summoning 🪄 @Asaf Cohen and @Shaul Kremer for insight

Hi @Philip Claesson 🙂 Could you please add your full docker compose / way you launch opal? Also please attach the full logs so we can investigate.

Hey again! We're deploying using the latest version of the opal-helm-chart. When properly investigating the env variables I think I may have figured it out. I noticed that my opal-client deployment has the data updater set twice:

OPAL_DATA_UPDATER_ENABLED:             true
OPAL_DATA_UPDATER_ENABLED:             false

I think the

true

comes from our values.yaml, the false one comes from this line. As we don't specify data sources through values.yaml but instead through envFrom from a secret (since it contains db credentials).

Cool. 😇 So just to verify - the problem is solved?

Not really - we need to modify the helm chart. Currently it makes assumptions about what is sent in via values.yaml while some things may actually be overridden via env variables from secrets. I'll draft a PR 🙂

Roger that - Thought you’d just switch to / propagate into the values.yaml. @Raz Co can you keep an eye on @Philip Claesson’s PR as it is coming in

Hey @Philip Claesson, I see your fresh new PR - I’m taking a look 🙂

Thanks @Raz Co! There are a bunch of different ways this could be solved I think, this is what I came up with. Hopefully the description helps explain it. https://github.com/permitio/opal-helm-chart/pull/51/ Basically, we need to support passing data source config via secret rather than via the helm chart (since the config may contain secret connection params).

Totally understand the need here. I’m planning to make a much smarter way to deal with these variables in the next major OPAL release.

Thanks for merging @Raz Co! That sounds really good. It just struck me, perhaps it ended up being a bit weird. Now we're looking for the env variable OPAL_DATA_UPDATER_ENABLED on the server config, and if it does not exist we set it on the client.

Nice catch ! Thanks, I merged this 🙂