-
Notifications
You must be signed in to change notification settings - Fork 44
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/1438 visible for groups within tool options #1449
Feature/1438 visible for groups within tool options #1449
Conversation
# For development and testing purposes, a user name can be supplied here. | ||
# Make sure to always disable this in production! | ||
#AD_OVERRIDE_USER_WITH_VALUE=someUser | ||
# AD_OVERRIDE_USER_WITH_VALUE=someUser | ||
# For development and testing purposes, groups can be supplied here. | ||
# Make sure to always disable this in production! | ||
# AD_OVERRIDE_USER_GROUPS_WITH_VALUE=someGroup1,someGroup2 |
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.
I had a quick look at the comment related to these keys and this got me thinking: should we be a bit harder on this and actually not allow these keys at all (or ignore their values in code), if NODE_ENV=production
(see line 24). What's your opinion?
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.
Yes, its a really good idea actually. Prevents .env accidents even more.
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.
Check added:
9fd17fa
Closes #1438