In order to simplify the codebase, a Dev needs to reach out to a Service Owner or Past team member about why there is a lot of duplicated endpoints in GWELLS (V1 v V2).
Solution Needs
Learn why many endpoints of API V1 and V2 are just clones of each other.
Identify these endpoints
Is there a reason we have Two sets of the same version?
Can We remove one, seeing as its a duplicate?
Is anyone/anything using this V1 service
Could we just redirect the request to v2
Or just delete the V1 class and use the V2 class
Are we only keeping these to preserve git history of the past devs?
Timebox
How much effort are we committing to this research?
Outcome
Details describing the outcome of the research
Was it successful? What direction should the work go?
In GWELLS you can look at Classes such as [WellExportListAPIViewV1, WellExportListAPIViewV1], [WellListAPIViewV1, WellListAPIViewV2] And see that they're just copies of each other. But these could just point to the same class, the only difference is a lack of Swagger documentation.
All the Postman tests we inherited have tests for V1 AND V2, In closer inspection these tests are the exact same, other than targetting /v1/ or /v2/ proving these endpoints are offering the exact same functionality
Is there a way to confirm that these endpoints are being hit? Can confirm by logging and taking look at logs in Kibana. Viewing endpoints being hit in django.
Problem Description
In order to simplify the codebase, a Dev needs to reach out to a Service Owner or Past team member about why there is a lot of duplicated endpoints in GWELLS (V1 v V2).
Solution Needs
Timebox
Outcome
Details describing the outcome of the research
Additional Context
/v1/
or/v2/
proving these endpoints are offering the exact same functionality