On 02/22/2013 08:31 AM, Dan Callaghan wrote:
Excerpts from Jan Stancek's message of 2013-02-21 20:49:28
+1000:
> Hi,
>
> would it make sense to add to harness API:
> GET /recipes/(recipe_id)/logs/(path)
> so harness could provide URL or content to test?
>
> One of the requests in past was to be able to get to your own console.log,
> so you can for example check output of kdump kernel.
Good idea, Jan. Thanks for the suggestion. I will add it to the doc.
It makes perfect sense as it matches PUT for the same URL.
I was actually going to ask about that - is there any reason not to have
GET counterparts for most of the URLs in the API? It would be nice not
to have to go through the main XML-RPC API in order to read back results
when testing a harness.
Cheers,
Nick.
--
Nick Coghlan
Red Hat Infrastructure Engineering & Development, Brisbane
Python Applications Team Lead
Beaker Development Lead (
http://beaker-project.org/)
PulpDist Development Lead (
http://pulpdist.readthedocs.org)