Darryl L. Pierce wrote:
On Fri, May 08, 2009 at 09:19:52AM -0400, Michael DeHaan wrote:
> If some one wants to keep them up2date with all recent cobbler changes
> and also give them object-edit support, they can stay, but we shouldn't
> keep them around if they can't do everything cobbler XMLRPC can do --
> it's a source of confusion for people trying to perform those
> operations. That would basically mean they would need to completely
> autogenerate all the "field" information at least. We are working on
> some APIs to do this for the CLI/webapp, would you be interested in
> making rubygem-cobbler autodiscover them and also teaching it to be able
> to perform edits?
>
I wouldn't mind that at all. It'd be an interesting challenge.
------------------------------------------------------------------------
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler-devel
Good deal!
Take a look at the get_fields stuff added on devel to the item_*.py
objects ... this is somewhat evolving but is how we're doing the
webapp, and soon this will also drive the command line parser generation
(I hope).
Methods like sync and reposync and such in remote.py may still have to
be manually added but it's not that bad.
We could probably also use some Wiki documentation on how to use the
module, if we don't already have any?
--Michael