-
Notifications
You must be signed in to change notification settings - Fork 661
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
Tracking specific environment variables #17
Comments
@eyalto How about this one (it will work in tandem with ArgParse, absl etc.):
|
This indeed results in the same effect but I was looking for a mechanism that is external to the code that can be configured somehow externally and minimises the footprint in the code I will take your advise and implement such mechanism inside our code - but it may be useful for other users / developers as well - if this is indeed the case .... |
@eyalto thank you for the feature suggestion.
Is that what you had in mind? |
This is even better than what I was thinking about
Will this be applied soon ?
…On Mon, Jul 1, 2019, 22:44 Martin.B ***@***.***> wrote:
@eyalto <https://github.com/eyalto> thank you for the feature suggestion.
Here is what I was thinking:
$ export TRAINS_LOG_ENVIRONMENT=
(default) *TRAINS* does not log OS environment variables
$ export TRAINS_LOG_ENVIRONMENT="PWD,PYTHONPATH"
Will result in *TRAINS* logging values of both PWD and PYTHONPATH
$ export TRAINS_LOG_ENVIRONMENT="*"
Will result in *TRAINS* logging values of ALL environment variables
Is that what you had in mind?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#17>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGQ7EDGS7IOWMF7BZ3OOQLP5JNADANCNFSM4H4VLEQA>
.
|
Hey! |
@shaulimaya great to hear you are already using this feature. |
Thanks a lot! |
@shaulimaya not sure security wise, this is recommended :) |
Closing, feature is now available in 0.10.2 |
Is there a way to provide a default list of environment variables that are not part of args that are tracked along with the experiment ?
If not can you add this as feature request ?
The text was updated successfully, but these errors were encountered: