hi there, we are trying to use terraform to deploy the opal server with the latest version on the helm chart and notice that you have committed this changes 25731f6 recently to change the the default values file 'dataConfigSources' section:
server:
.........
dataConfigSources:
# Option #1 - No data sources
config:
entries: []
which currently cause an issue when we set the value for external_source_url as follow:
server:
dataConfigSources:
external_source_url: "http://xxx-xxx-xx-xxx"
When we deploy via terraform it will set the environment variable OPAL_DATA_CONFIG_SOURCES to {"config":{"entries":[]},"external_source_url":"http://xxx-xxx-xx-xxx"} and opal server is throwing the following error:
pydantic.error_wrappers.ValidationError: 1 validation error for ServerDataSourceConfig
root
you must provide ONLY ONE of these fields: config, external_source_url (type=value_error)
I think thats why the default values file was initially set with external_source_url as the first options rather than having the config -> entries as the first options.
I'm wondering if you able to revert this that part of the code changes in the value file or update the server template file to fix this issue.
hi there, we are trying to use terraform to deploy the opal server with the latest version on the helm chart and notice that you have committed this changes 25731f6 recently to change the the default values file 'dataConfigSources' section:
which currently cause an issue when we set the value for external_source_url as follow:
When we deploy via terraform it will set the environment variable OPAL_DATA_CONFIG_SOURCES to {"config":{"entries":[]},"external_source_url":"http://xxx-xxx-xx-xxx"} and opal server is throwing the following error:
pydantic.error_wrappers.ValidationError: 1 validation error for ServerDataSourceConfig
root
you must provide ONLY ONE of these fields: config, external_source_url (type=value_error)
I think thats why the default values file was initially set with external_source_url as the first options rather than having the config -> entries as the first options.
I'm wondering if you able to revert this that part of the code changes in the value file or update the server template file to fix this issue.