Well it needs to be deprecated first, but as of right now it could be deprecated in 3.x and removed in 4.x
On Tue, Apr 26, 2022, 15:54 Jeremy Mitchell <mitchell...@gmail.com> wrote: > does it first need to be deprecated before being removed? i.e. deprecated > in 4.x and removed in 5.x > > On Tue, Apr 26, 2022 at 1:15 PM ocket 8888 <ocket8...@gmail.com> wrote: > > > AFAIK the only difference between this and /servers is that > > /servers/details is missing some things (e.g. routerPortName) that > > exist on /servers servers, but they have this "hwinfo" property. Even > > in APIv1 /hwinfo was read-only and now that endpoint no longer exists > > (removed in v2). "Hwinfo" as a concept has sort of passed into > > obscurity as new servers can't have it as of at least a little more > > than a year ago. > > > > Remembering to update an unused endpoint is difficult, and actually > > doing so is annoying. As a result, the object definitions between > > /servers and /servers/details have drifted to the point that I'm not > > sure how the latter could possibly be useful anymore. Which will > > likely continue unless we just get rid of it. > > >
