[katello-devel] The State of API V2

[Martin Bacovsky]

On 06/22/2013 09:23 PM, Eric D Helms wrote:
> A few months back a new version of our API was merged into master. 
> Since that time, I get the feeling most developers do now know what to 
> do with API V2, and I am unaware of any migration plans to account for 
> this new version. Could someone shed some light on the plans around V2 
> and what we as developers are supposed to be doing with it?
>
> Thanks,
> Eric
>
There are actually no plans I'm aware of. The API V2 is ready a can be 
used right away. The motivation for work on v2 was need for unification 
of routes, output, error handling and input parameters before we start 
with refactoring and unification of Katello CLI. However the work on 
Katello CLI was postponed. The conventions and howto for developers can 
be found in [1]. For now it seems reasonable to develop both v1 and v2 
(in new calls it usually just means to add route and inherit empty class 
from v1)

The only part of Katello that uses API is afaik the CLI which needs to 
be updated to use the v2. In Foreman we are currently working on new CLI 
written in Ruby [2], [3] using Apipie bindings and the results look 
promising . If Katello team decides to go the same way I would suggest 
to switch to  v2.

Martin

[1] https://fedorahosted.org/katello/wiki/APIConventions
[2] https://github.com/mbacovsky/foreman_cli_draft
[3] https://www.youtube.com/watch?feature=player_embedded&v=coeFR_KnXgM 
(Deep dive)