Page Comparison

...

• Remove such records before sending the file

• Modify code to skip/process the record

Transition Plan

1. Current Status

2. Future Roles and Responsibilities

3. New and Outstanding issues

4. Documentation Sources

   • Github Wiki (product Documentation)

   • Confluence Space (Project documentation for working documents)

   • MS Teams/SharePoint (comms and files storage)

5. /wiki/spaces/CCP/pages/1269170228

   • Technical Lead (Will discuss these on the May 23rd Meeting)

     • Github (product code)

     • AWS Public Cloud Hosting of various components of the application

       • The deployed application "DROP"

       • The File Storage or "S3 Buckets"

         • SFTP Site 

           • location where ServiceBC (SBC) drops their GARMS JSON file

           • location where Banking and Cash Management (BCM) drops their DAT file

         • The location where reports are stored

         • AWS Transfer Family

           • pulls from the BCM SFTP Site.

           • find out how it is being done to get the GARMS files into S3

     • GC Notify Account (the service that handles email notifications)

     • API Services Portal (future service to replace the SMTP

   • Product Owner

     • Jira Project (Project backlog)

6. Financial Items 

   • AWS hosting costs 

   • MOU between the business area a platform services who pay the AWS Hosting invoices on our behalf

   • S3 Storage Metrics: DROP-S3-Storage - S3 Storage Lens dashboard | S3 | ca-central-1 (amazon.com)

7. Follow-up meetings to carry out the transition plan