This message was deleted.
# opal
s
This message was deleted.
r
Hey @Edoardo Viviani, What is the issue that you are encountering with ? is there any error printed ?
Oh I see you edited the message now 🙂
e
yes sorry, i accidentally sent the message before completing it
the environment var
OPAL_DATA_CONFIG_SOURCES
gets always filled with both config (containing an empty array) and external source url, i have to remove it manually after the deployment
ops, i’ve just seen your issue open on gh https://github.com/permitio/opal-helm-chart/issues/48
p
Took a quick look, I think it may come from the default value of dataConfigSources.config which is '[]' in values.schema.json.
@Edoardo Viviani, does it work if you set:
Copy code
dataConfigSources:
    external_source_url: https://***.lambda-url.eu-central-1.on.aws/
    config: null
e
it does not, i have tried it before but i just double checked,
"config": {}
is still added to the
OPAL_DATA_CONFIG_SOURCES
env
r
Hey @Edoardo Viviani , it’s been couple of very busy days for our team. Let me try to tackle this in the next few days, hope the workaround is good enough for now.
Hey @Edgar Littleman, Can you try to set your dataConfigSources like this -
Copy code
dataConfigSources:
    config: null
    external_source_url: "<http://www.external><http://_source_url.com|_source_url.com>"
I plan to completely change the validation on the schema there, it’s not 100% right now as it’s very confusing to use. Let me know if this works for you.
e
Hi Raz, that does not seem to help, as k8s keeps the old containers running until the new ones succeed their healthcheck, i have all the time to manually go into their deployment settings and fix it and we do not need to redeploy it often, it’s just a minor inconvenience. Thank you for your help anyways!
r
I’m happy its not a big issue but It’s obviously not enough for us, we’re aiming for a full working helm chart ! 🌈 Let me dig deeper into this and update you