Closed
Description
Database Migration
User Story - Business Need
AWS confirmed that a PoolID can be up to 256 characters so we need to allow the ServiceSmsSender.sms_sender
field to have that many characters.
- Ticket is understood, and QA has been contacted (if the ticket has a QA label).
User Story(ies)
As a Service using VA Notify
I want to send to the Veteran without specifying a phone number to use for each request
So that I do not have to track extra data or do VA Profile lookups prior to calling VA Notify
As VA Notify
I want to use AWS Pools to send domestic and international
So that our clients can use one sender for a use case
Additional Info and Resources
- send_text_message boto3 method
Acceptance Criteria
- The
ServiceSmsSender.sender
field allows 256 characters - "doc" parameter specifies it is for: PhoneNumber, PhoneNumberId, PhoneNumberArn, SenderId, SenderIdArn, PoolId, or PoolArn, or it is updated to be more accurate and the AWS docs are linked as a comment
-
Schema/swagger update if necessaryThe field length is not mentioned in the docs. - Unit test with 256+ characters should fail
- This work is added to the sprint review slide deck (key win bullet point and demo slide)
QA Considerations
Potential Dependencies
None.