Excerpts from Nick Coghlan's message of 2013-02-22 12:25:03 +1000:
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.
The recipe XML gives back everything that you can create or modify
(status, results, logs, ...) so you can just use that.
But I agree, for completeness it might be nice to allow GETs on
everything and return some kind of sensible response.
--
Dan Callaghan <dcallagh(a)redhat.com>
Software Engineer, Infrastructure Engineering and Development
Red Hat, Inc.