icgc-argo/daco2ego

Utility and service to load DACO list into Ego.

daco2ego's Issues

Ego POC with Google as ID Provider - Documentation

• Once POC is complete and tested, document the changes that were required to get the POC to function. This will be used to break down the work further and begin the MVP implementation of the changes

Integrate dac-api the Daco2Ego Argo

Change the Daco2Ego Argo

• Should accept 2 files at the time of run: the file from the ARGO isilon and the file generated by the DACO system
• Add steps to:
  • Downloads the new file from dac-api endpoint
  • Concatenate the 2 files
  • Deduplicate users in the concatenated file.
  • Run the current working Daco2Ego process.

[ICGC-ARGO] Coordinate V1 Shutdown with IT

Coordinate Daco V1 shutdown with IT as relates to Daco2Ego for ICGC-ARGO

Required by SoftEng To Do:

• Update ICGC-ARGO Daco2Ego app --> Remove all references to v1 files to prevent script from crashing. Requires interaction with IT --> Changes must be merged and deployed in production before IT shuts down V1
• Update ICGC25K DCC Daco2Ego app --> Remove all references to v1 files to prevent script from crashing. Requires interaction with IT --> Changes must be merged and deployed in production before IT shuts down V1 (to be done in another ticket icgc-dcc#32)
• Email EGA (Aina, cc: Andrea Mero) --> Courtesy email to EGA to inform them they will receive only one list going forward
• Email DACO Admin (Judith, Amber) --> Courtesy email to DACO admins to inform them V1 has been shut down (Melanie emailed Judith/Amber May 16, 2023 for final confirmation we can proceed with V1 shutdown)

Not Required:

• Archiving of v1 resources (confirmed with Melanie/Amber/Judith)

[ICGC-ARGO] Remove V1 file reference

Remove V1 file references from initialization and config. V1 system will be shutdown entirely 20/11/22

ARGO - Add permissions for DACO2Ego ARGO to allow access to API endpoint on DACO v2 to retrieve approved list