Mock VA21a API #16501
Closed
Mock VA21a API #16501
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
Closed
1 task
|
This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
|
This PR has been closed because it has had no activity for 37 days |
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.
Summary
This is the result of technical discovery on how to integrate external APIs with a new VA.gov form. It adds an endpoint for submitting VA21a forms that proxies the request to a mock API found here. This endpoint expects a user authenticated via the ARP audience.
The PR also extracts saving in-progress form API functionality into a standalone Rails module,
in_progress_forms. At the time of draft PR, the module will only work for users authenticated via the vagov audience, not ARP, so further work is necessary to get this working for representative.va.gov without disrupting existing VA.gov users.