[katello-devel] How should we post objects

Lukas Zapletal lzap at redhat.com
Wed Jul 18 07:49:24 UTC 2012


Uh, I completely missed the doco link:

https://fedorahosted.org/katello/wiki/APIConventions

Disregard my first mail, we do wrap! I would suggest to generate the
final API documentation for CFSE V1 (how close are we?) and then we can
start changing it.

LZ

On Tue, Jul 17, 2012 at 02:20:03PM +0200, Tomas Strachota wrote:
> On 07/16/2012 03:38 PM, Bryan Kearney wrote:
> >On 07/13/2012 11:07 AM, Dmitri Dolguikh wrote:
> >>The difference between creating a new object and updating an existing
> >>one is (in the context of this discussion) in idempotency: repeated
> >>calls to create an object may return a new object every time, while
> >>making the same change over and over again should result in the same
> >>state of the object. So: POST is for creation, PUT is for updates.
> >>
> >
> >Agree. My main qustion is if I should be opening bugs where the json
> >which is postd does not have the following:
> >
> >object_name: {
> >attr: "foo"
> >}
> >
> >an instead has:
> >
> >{
> >attr: "foo"
> >}
> >
> >-- bk
> >
> 
> I'm for opening bugs in such cases and working towards consistency.
> 
> As far as I remember from the previous discussion more people seemed
> to like using {obj_name: {...}} pattern as it had slightly more
> advantages.
> 
> T.
> 
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel

-- 
Later,

 Lukas "lzap" Zapletal
 #katello #systemengine




More information about the katello-devel mailing list