-
Notifications
You must be signed in to change notification settings - Fork 63
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
use email address for unique-ish id for feature toggles #3323
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
annaswims
force-pushed
the
change_feature_toggle_id
branch
from
September 20, 2019 17:21
929c8b9
to
09ef709
Compare
va-vfs-bot
temporarily deployed
to
change_feature_toggle_id/master
September 20, 2019 21:28
Inactive
va-vfs-bot
temporarily deployed
to
change_feature_toggle_id/master
September 23, 2019 15:01
Inactive
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.
LGTM, but I'm a bit OOL in considering what negative consequences may arise from such a change.
jholton
approved these changes
Sep 23, 2019
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.
LGTM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of change
I think we would be better off using email address as the identifier for our feature toggles. It's a lot easier to manage, say if we want to enable a feature for a specific user like this:
Otherwise we'd have to ask the user to log in and find their uuid, which is cumbersome.
The user code allows for nil email addresses (though I thing we always have one), so on the odd chance they don't have one we can fall back to using account_uuid.
Presuming the user uses the same email address across their DS Logon/ID.me/MHV accounts they would see the same behavior across login types
ruby toggle_threshold.rb my_feature_name
Testing done
tested locally that I could enable an individual actor by email address
Testing planned
verify on staging
Applies to all PRs