On Wed, Sep 01, 2010 at 07:47:50AM +0200, Tollef Fog Heen wrote: > ]] Dominic Hargreaves
> | Either way, I'm fairly sure that this would be considered an enhancement > | rather than defect by upstream (the REST interface doesn't really cover > | administration, just day to day operation), so setting severity accordingly. > > It would be really useful if all functionality in RT is exposed through > the REST interface. I guess that might be a fairly significant effort, > though. :-) > > Until then, it would be useful if the limitations are documented, and if > possible, what workarounds are available. Sure. Just for completeness here, then, before I have a chance to write some documentation: The RT native perl API is pretty usable once you get used to it, but unfortunately isn't that well documented. Have a browse through the core code to get a feel for the object model and calling API. It's actually on my todo list at work to automate queue creation in a similar way :) Obviously this only works if you are in a position to run code with the same database access as the RT application server itself. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
