Closed wwelling closed 1 month ago
I really wish we limited out languages for the migration scripts. We already have Ruby. We have many of the fixes via SQL. Adding Node makes this just more complicated.
I have discussed with James S regarding merging migration scripts as much as possible. The node script from Vireo 3 to Vireo 4 database can and should be an update in TAMU customized ruby scripts. The second node script can be added to the ruby script as to make requests to the directory search API for retrieving UIN by netid when not in Vireo 3 database but will require additional dependencies and more complicated logic than the external node script.
Sprint 2 deployment migration
Here is a node.js script to update Vireo 4 weaver_users netid to be institutionalidentifier (UIN) from Vireo 3. If UIN not available, it will use netid (unique hash) or email.
Here is a node.js script to request individual record from directory search ID office provides to retrieve UIN to update netid.
https://docs.security.tamu.edu/docs/identity-security/attribute-services/api/directory_search/