-
Notifications
You must be signed in to change notification settings - Fork 212
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
EVSS PCIU Migration: Step 6b: Remove PCIU configuration and references from Vets-API (non-prefill) #76175
Comments
Moving out 2 sprints. This work should happen after ContactInformation is complete. ContactInformation is replacing PCIU, these tickets cannot be worked on until ContactInformation has been done and the PCIU has been replaced. |
Contact Information V2 has to replace PCIU in prod before PCIU references can be removed. |
Standup note: Moving this ticket to blocked status, as it is intricately related to and blocked by Step 6a. Also, Step 6a has a dependency with the mobile migration and testing and a draft PR can be created but it cannot be merged until the mobile work is complete. |
Sprint reporting note: this ticket is blocked until the mobile testing is complete. Moving out to Sprint 20, but I will comment & unblock this ticket if the mobile testing happens to get completed during Sprint 19. |
User Story
As a developer, I want to remove all references of PCIU to ensure Vets-API does not use PCIU, as we transition to VA Profile in preparation for the PCIU deprecation
Issue Description
PCIU configuration and references in Vets-API are no longer needed and should be removed to clean up the codebase and reduce unused configuration. This includes all references that are NOT related to prefill, including configurations and specs
remove_pciu
flipper still allows PCIU data to fill in when data is missing.remove_pciu_2
does not allow PCIU data to fill in when data is missing. Any reference to bothremove_pciu
andremove_pciu_2
flippers will need to be removed with the following tasks:Tasks
Acceptance Criteria
The text was updated successfully, but these errors were encountered: