Skip to content
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

Allow overriding default location with environment variable #19

Open
wcooley opened this issue Mar 10, 2017 · 1 comment
Open

Allow overriding default location with environment variable #19

wcooley opened this issue Mar 10, 2017 · 1 comment

Comments

@wcooley
Copy link

wcooley commented Mar 10, 2017

I would like to be able to override the default path with an environment variable, like GENDERS_FILE (or maybe just GENDERS?).

I use genders on my laptop and desktop and maintain my genders file in a git repo. Unlike our servers, my laptop and desktop are not under configuration management, so it's messy to keep /etc/genders updated -- I have to symlink to my checkout in my home directory, manually override the path whenever I run nodeattr or manually copy the updated file into place.

I can also imagine scenarios where an individual user might want to use genders/pdsh and, while she might be able to convince her sysadmins to install the packages, having them maintain a shared database is more problematic. Being able to use a personal copy would be a good first step to bringing the tool into a new environment.

I can also imagine potential security implications with allowing users to override the location, if genders/nodeattr/pdsh are used in scripts run with elevated privileges, so it would probably be necessary to include a compile-time flag to disable this feature for sites that might have such requirements.

@chu11
Copy link
Member

chu11 commented Mar 10, 2017

I can also imagine scenarios where an individual user might want to use genders/pdsh and, while she might be able to convince her sysadmins to install the packages, having them maintain a shared database is more problematic

I think this is a good use case example.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants