Skip to content
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

Open
13 tasks
Tracked by #73776
RachalCassity opened this issue Feb 14, 2024 · 4 comments

Comments

@RachalCassity
Copy link
Member

RachalCassity commented Feb 14, 2024

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 both remove_pciu and remove_pciu_2 flippers will need to be removed with the following tasks:

Tasks

  • Remove lib/evss/pciu
  • Remove lib/evss/pciu_address
  • Remove from rubocop
  • Remove from breakers
  • Remove from FormProfile
  • Remove from User model
  • Remove related spec files
  • Remove redis configuration
  • Remove settings config
  • Tests are passing
  • Test locally
  • Test in staging

Acceptance Criteria

  • PCIU configurations listed under the tasks have been completely removed from Vets-API
@jennb33 jennb33 added needs-grooming Use this to designate any issues that need grooming from the team 2024 PCIU labels Feb 14, 2024
@jennb33 jennb33 removed the needs-grooming Use this to designate any issues that need grooming from the team label Feb 21, 2024
@RachalCassity RachalCassity changed the title Last Item: Ensure PCIU references have been removed EVSS PCIU Migration: Objective 7: Ensure PCIU references have been removed Mar 21, 2024
@jennb33 jennb33 changed the title EVSS PCIU Migration: Objective 7: Ensure PCIU references have been removed EVSS PCIU Migration: Step 7: Ensure PCIU references have been removed Mar 26, 2024
@jennb33 jennb33 removed the blocked label Aug 5, 2024
@jennb33 jennb33 changed the title EVSS PCIU Migration: Step 7: Ensure PCIU references have been removed EVSS PCIU Migration: Step 5: Ensure PCIU references have been removed Sep 23, 2024
@AshleyGuerrant
Copy link

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.

@RachalCassity RachalCassity changed the title EVSS PCIU Migration: Step 5: Ensure PCIU references have been removed EVSS PCIU Migration: Final Step: Ensure PCIU references have been removed Dec 5, 2024
@RachalCassity
Copy link
Member Author

Contact Information V2 has to replace PCIU in prod before PCIU references can be removed.

@AshleyGuerrant AshleyGuerrant changed the title EVSS PCIU Migration: Final Step: Ensure PCIU references have been removed EVSS PCIU Migration: Final Step (b): Ensure PCIU references have been removed Dec 11, 2024
@AshleyGuerrant AshleyGuerrant changed the title EVSS PCIU Migration: Final Step (b): Ensure PCIU references have been removed EVSS PCIU Migration: Step 6 (b): Ensure PCIU references have been removed Dec 11, 2024
@AshleyGuerrant AshleyGuerrant changed the title EVSS PCIU Migration: Step 6 (b): Ensure PCIU references have been removed EVSS PCIU Migration: Step 6b: Ensure PCIU references have been removed Dec 12, 2024
@AshleyGuerrant AshleyGuerrant added the needs-refinement Identifies tickets that need to be refined label Dec 16, 2024
@RachalCassity RachalCassity changed the title EVSS PCIU Migration: Step 6b: Ensure PCIU references have been removed EVSS PCIU Migration: Step 6b: Remove PCIU configuration and references from Vets-API Dec 17, 2024
@RachalCassity RachalCassity changed the title EVSS PCIU Migration: Step 6b: Remove PCIU configuration and references from Vets-API EVSS PCIU Migration: Step 6 (b): Remove PCIU configuration and references from Vets-API Dec 17, 2024
@RachalCassity RachalCassity marked this as a duplicate of #99430 Dec 18, 2024
@AshleyGuerrant AshleyGuerrant removed the needs-refinement Identifies tickets that need to be refined label Dec 18, 2024
@AshleyGuerrant AshleyGuerrant changed the title EVSS PCIU Migration: Step 6 (b): Remove PCIU configuration and references from Vets-API EVSS PCIU Migration: Step 6 (b): Remove PCIU configuration and references from Vets-API (non-prefill) Dec 18, 2024
@AshleyGuerrant AshleyGuerrant changed the title EVSS PCIU Migration: Step 6 (b): Remove PCIU configuration and references from Vets-API (non-prefill) EVSS PCIU Migration: Step 6b: Remove PCIU configuration and references from Vets-API (non-prefill) Dec 18, 2024
@AshleyGuerrant
Copy link

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.
Work on this ticket can start either after the draft PR is created for Step 6a, or after the mobile migration and testing is merged.

@AshleyGuerrant
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants