-
Notifications
You must be signed in to change notification settings - Fork 13
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
Support GEL_XXX environment variables #96
Conversation
if [ -z "${file_var_val}" ] && [ -n "${old_file_var_val}" ]; then | ||
file_var_val="${old_file_var_val}" | ||
unset "$old_file_var" | ||
if [ "$var" == "GEL_SERVER_PASSWORD" ] || [ "$var" == "GEL_SERVER_PORT" ]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this necessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because we recognize the client version of these two variables GEL_PASSWORD
and GEL_PORT
. But only for those two.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you point to where exactly these are handled? AFAICS neither the entrypoint nor the server itself handle these.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The usage is obfuscated with bash variable interpolation. Before this PR:
The check here would give a deprecation warning for the client form of envvars EXCEPT for EDGEDB_PORT
and EDGEDB_PASSWORD
see edbdocker_env_var_deprecated.
Then the value of these variables is used here.
We also use EDGEDB_PASSWORD
in a test composed app works.
Co-authored-by: Elvis Pranskevichus <[email protected]>
Co-authored-by: Elvis Pranskevichus <[email protected]>
No description provided.