-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
82557: Add all the logic to handle DB insertion with uploads controller #16701
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
va-vfs-bot
temporarily deployed
to
82557-part-a-map-pega-responses-to-be/main/main
May 9, 2024 20:12
Inactive
…emove primary contact info from metadata to Pega
michaelclement
previously approved these changes
May 9, 2024
cloudmagic80
previously approved these changes
May 9, 2024
va-vfs-bot
temporarily deployed
to
82557-part-a-map-pega-responses-to-be/main/main
May 9, 2024 21:53
Inactive
balexandr
dismissed stale reviews from cloudmagic80 and michaelclement
via
May 10, 2024 13:58
cf0e4e3
va-vfs-bot
temporarily deployed
to
82557-part-a-map-pega-responses-to-be/main/main
May 10, 2024 13:59
Inactive
michaelclement
previously approved these changes
May 10, 2024
cloudmagic80
previously approved these changes
May 10, 2024
balexandr
dismissed stale reviews from cloudmagic80 and michaelclement
via
May 10, 2024 17:27
9fe253a
va-vfs-bot
temporarily deployed
to
82557-part-a-map-pega-responses-to-be/main/main
May 10, 2024 18:00
Inactive
va-vfs-bot
temporarily deployed
to
82557-part-a-map-pega-responses-to-be/main/main
May 10, 2024 18:28
Inactive
va-vfs-bot
temporarily deployed
to
82557-part-a-map-pega-responses-to-be/main/main
May 10, 2024 18:56
Inactive
michaelclement
previously approved these changes
May 10, 2024
va-vfs-bot
temporarily deployed
to
82557-part-a-map-pega-responses-to-be/main/main
May 10, 2024 20:55
Inactive
cloudmagic80
previously approved these changes
May 10, 2024
balexandr
dismissed stale reviews from cloudmagic80 and michaelclement
via
May 14, 2024 22:26
3389cc3
va-vfs-bot
temporarily deployed
to
82557-part-a-map-pega-responses-to-be/main/main
May 15, 2024 00:24
Inactive
michaelclement
approved these changes
May 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In support of sending an email update to a VFMP applicant, the PEGA response that represents the applicants data needs to be stored in the VA.gov back end.
This is Part A of this ticket as it handles the initial DB insertion and setup for part B
Summary
Related issue(s)
Screenshots
Testing done
Acceptance criteria
Given a well-formed call to the callback endpoint
When the response is received
Then the response should be persisted so that status can be send back to the applicantexpected