Automatically sync users between SNEx1 and SNEx2 #31
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
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.
This PR introduces changes to sync new users and modifications to existing users between SNEx1 and SNEx2. The commits so far lay out the groundwork for automatically syncing user information added in SNEx1 to SNEx2, as well as modifications to the base TOM Toolkit to migrate user modifications made in SNEx2 to SNEx1. Still left to do is setting up mysql triggers in the SNEx1 database to populate the
db_changestable with new, modified, or deleted user rows. Also left on the SNEx2 side is to set up user registration in SNEx2 and integrate those additions with this machinery to sync newly registered users with SNEx1, although this may be left to another PR in the future.