Extract admin endpoints from the rest client to an admin client.

[carlesarnal]

No description provided.

[jhughes24816]

Could someone please provide some details as to what this issue is about?

[famarting]

sure, it just means to separate the methods here in two different interfaces, one for the /admin part of our API and another one for the rest

[famarting]

also important to mention that we should always have in mind backwards compatibility, and therefore do this kind of changes in a way that don't break user's code. We should first deprecate the methods in the old interface while creating a new Admin interface, and later on (i.e. two releases after) remove the deprecated methods

[jhughes24816]

Okay, thanks. Couple of follow up questions:

1. Currently going through the v1/openapi.json and v2/openapi.json, in v2 I found /admin end points. Are there any end points in v1 that would be considered admin e.g. possibly /rules?
2. With the interfaces split, would it be useful to split the RegistryClientImpl in a similar way?

[famarting]

the v1 api is just kept for compatibility with old clients. the current interface RegistryClient and it's implementation only targets the latest version of our API, in this case v2.