-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[🚀 Feature]: Use Environment Variables to set driver locations #14045
Comments
This is a nit. But why is Java label added to this issue? I might be missing something. |
The idea is to leave a path for users who want to avoid Selenium Manager completely. The decision was to implement an env var that the service would use. I guess we can keep the system properties in Java instead of implementing the env var. |
I included it intentionally because perhaps Java should look for the System Property and the Environment Variable? |
Actually, which convention do we want to match? For instance in Java: Options: |
I am in favour of having a consistent way across bindings, if that is possible. |
|
@pujagani @titusfortner I'm working on this hopefully I will put it for review this weekend :) |
#14287 added Ruby part and the following variables:
|
I can work on the Python functionality. |
The python part has also been implemented. In a2cacc1 and uses the same environment variables as Ruby. |
Feature and motivation
We discussed in the Selenium Dev Summit about having the ability to set driver location system-wide using environment variables, similar to how Java currently uses System Properties.
See #13806
Usage example
If we match Java System Properties, it would look like:
The text was updated successfully, but these errors were encountered: