Retire a decommissioned third-party endpoint
A third-party endpoint with a shutdown date, migrated before the date rather than after.
The ticket
Migrate every caller off a third-party endpoint that is being decommissioned.
Acceptance criteria
- No caller references the old endpoint
- Each migrated caller has a test against the new one
- The old client code is deleted
- The shutdown date is recorded in the description
What lands as proof
A search showing no remaining references, plus tests against the replacement at each site.
Why teams defer it
- The date is far away when the notice arrives and close when somebody rereads it.
- Notices land in an inbox rather than a backlog, so they are easy to lose.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: migrate every caller off a third-party endpoint that is being decommissioned. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means every caller migrated, the old client deleted, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.