Logically Determine Which Celery Tasks To Call - SMS

[k-macmillan]

User Story - Business Need

va-enp-api will be able to handle all validation, but lookup VA Profile ID, gathering contact information, and actually sending the notification are all tasks that Celery will still do at first. This method identifies which tasks need to be called and logs them. A future ticket will implement the SQS send_message functionality.

• Ticket is understood, and QA has been contacted (if the ticket has a QA label).

User Story(ies)

As a VA Notify dev
I want to know what tasks a notification still needs to accomplish
So that we can prepare to send them to the appropriate tasks

Additional Info and Resources

These are the three applicable methods:

• lookup_va_profile_id - MPI call to get a VA Profile ID
• lookup_contact_info - VA Profile call to get contact information and preferences
• deliver_sms - Sends an sms

Acceptance Criteria

• Logic is based on phone_number and recipient_identifier fields
• phone_number results in only a deliver_sms task
• recipient_identifier results in an MPI lookup if it's not a VA Profile ID, then a contact lookup, then deliver the sms
• The output is logged so we can test the logic
• This work is added to the sprint review slide deck (key win bullet point and demo slide)

QA Considerations

Potential Dependencies

Out of Scope

A separate ticket will implement the ETL methods necessary to actually put the desired tasks into SQS.