Currently we have a single path for the sockpuppet API. In order to introduce more features and maintain backwards compatibility, the API should be versioned. When we make a a 1.0.0 release, the API should be accessible under a path starting with /v1 and so on, with the ability to manage new versions of the API via simple routing changes.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T259471 Sockpuppet detection API [low effort] | |||
| Resolved | None | T265722 New Service Request: Sockpuppet Detection | |||
| Open | None | T269778 Introduce API versioning to Sockpuppet |
Event Timeline
Comment Actions
Are we not planning on implementing this? If so, I'm okay to close. But I think it's still a worthwhile goal, if not for PET then for AHT or another team
Comment Actions
Err... no. We should implement this, and the task should not be closed. I thought we had a CR in flight, but I was wrong. Apologies for the noise.
Comment Actions
Adding Platform Engineering as Platform Team Workboards (Green) was archived and as open tasks should have an active project tag
Comment Actions
Not sure what to do to be honest, but closing seems like the easiest option - there are a lot of good-idea-but-when tickets in the Sockpuppet epic