-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failing to set client_options for ElasticSearch backend #248
Labels
Comments
Looks like it only occurs while running the $ bin/ralph runserver -b es --es-client-options verify_certs=True Output (truncated) logs:
If we take a look at the temporary settings:
The |
wilbrdt
added a commit
to wilbrdt/ralph
that referenced
this issue
Jan 10, 2023
Following issue openfun#248, rework/fix of the way the client_options are validated for es and mongo database backends, now as pydantic sub models.
wilbrdt
added a commit
to wilbrdt/ralph
that referenced
this issue
Jan 10, 2023
Following issue openfun#248, rework/fix of the way the client_options are validated for es and mongo database backends, now as pydantic sub models.
wilbrdt
added a commit
to wilbrdt/ralph
that referenced
this issue
Jan 11, 2023
Following issue openfun#248, rework/fix of the way the client_options are validated for es and mongo database backends, now as pydantic sub models.
wilbrdt
added a commit
to wilbrdt/ralph
that referenced
this issue
Jan 11, 2023
Following issue openfun#248, rework/fix of the way the client_options are validated for es and mongo database backends, now as pydantic sub models.
wilbrdt
added a commit
to wilbrdt/ralph
that referenced
this issue
Jan 12, 2023
Following issue openfun#248, rework/fix of the way the client_options are validated for es and mongo database backends, now as pydantic sub models.
wilbrdt
added a commit
that referenced
this issue
Jan 12, 2023
Following issue #248, rework/fix of the way the client_options are validated for es and mongo database backends, now as pydantic sub models.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Expected behavior/code
Using the --es-client-options to set a new CA certificate for ElasticSearch backend should not raise an error.
Actual Behavior
Fatal error :
Steps to Reproduce
bin/ralph runserver -b es --es-client-options ca_certs=toto
Environment
The text was updated successfully, but these errors were encountered: