Page MenuHomePhabricator

Introduce API versioning to Sockpuppet
Open, Needs TriagePublic


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.

Related Objects

Event Timeline

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

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.

Adding Platform Engineering as Platform Team Workboards (Green) was archived and as open tasks should have an active project tag

Not sure where this task belongs now.
Maybe we should close and re-open if the similarusers API is revived. @hnowlan would that be ok with you?

We should also follow the practices developed by the API Platform team.
cc / @sdkim

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