Discovery on PCIU usage was previously done on ticket #64189, and focused primarily on the pre-fill functionality. Some of that involved the PCIU_Address service, which was a wrapper around EVSS PCIU calls. Another consumer of this service is the addresses controller, which appeared to have no direct calls against it coming from vets-website by the 526ez application. There were, however, some evidence of their use by other applications due to some tests that were found. It is also possible that 526ez could be using address controller calls from other applications indirectly, and therefore could still be affected by an EVSS sunset.
Therefore, we'd like to do a more thorough investigation of the front end to have more confidence that all PCIU usage has been identified. If it is found that other applications are still using PCIU, we should inform the teams who are responsible for the affected code, so that they can then remove it in a more informed way. We should also explore using DataDog to track down address controller activity, in conjunction with front end code exploration.
Tasks
[ ] Identify any direct or indirect use of address controller calls from vets-website by the 526ez application
[ ] If possible, identify any direct use of address controller calls by other applications
[ ] Inform the relevant teams of this use via slack
Acceptance Criteria
[ ] Document all found address controller usage found here (or start a new wiki)
[ ] Create tickets to address any address controller usage by 526ez. Pun intended.
How to configure this issue
[ ] Attached to a Milestone (when will this be completed?)
[ ] Attached to an Epic (what body of work is this a part of?)
[ ] Labeled with Team (product support, analytics-insights, operations, service-design, Console-Services, tools-fe)
[ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
[ ] Labeled with Type (bug, request, discovery, documentation, etc.)
Issue Description
Discovery on PCIU usage was previously done on ticket #64189, and focused primarily on the pre-fill functionality. Some of that involved the PCIU_Address service, which was a wrapper around EVSS PCIU calls. Another consumer of this service is the addresses controller, which appeared to have no direct calls against it coming from vets-website by the 526ez application. There were, however, some evidence of their use by other applications due to some tests that were found. It is also possible that 526ez could be using address controller calls from other applications indirectly, and therefore could still be affected by an EVSS sunset.
Therefore, we'd like to do a more thorough investigation of the front end to have more confidence that all PCIU usage has been identified. If it is found that other applications are still using PCIU, we should inform the teams who are responsible for the affected code, so that they can then remove it in a more informed way. We should also explore using DataDog to track down address controller activity, in conjunction with front end code exploration.
Tasks
Acceptance Criteria
[ ] Create tickets to address any address controller usage by 526ez. Pun intended.
How to configure this issue
product support
,analytics-insights
,operations
,service-design
,Console-Services
,tools-fe
)backend
,frontend
,devops
,design
,research
,product
,ia
,qa
,analytics
,contact center
,research
,accessibility
,content
)bug
,request
,discovery
,documentation
, etc.)