On 9/2/2019 9:06 PM, Clint Adams wrote:
> On Mon, Sep 02, 2019 at 06:40:24PM +0200, Philipp Kern wrote:
>> I would prefer JSON as an input format, looking roughly like this:
>>
>> [{"pkg": "haskell-active", "ver": "0.2.0.13-6", "archs": ["mipsel",
>> "mips64el"], "suite": "sid", "reason": "semigroupoids changed from 5.2.2 to
>> 5.3.2"}]
>
> Something like https://people.debian.org/~clint/binNMUs-haskell.json ?
Yup, that passes my parser. But it doesn't answer the question I tried
to ask: How would I signal success/failure properly? And, even more
crucially, how would I signal partial success?
I could settle for two different blobs to return: One text blob in case
something in authz/validation went wrong and one JSON blob in case the
script successfully validated the input and then return "result":
"success"/"failure" (say, maybe with some more data from wannna-build)
on every single entry. I suppose in the first case it'd be an inline
response and in the second a file attachment. But then again you'd need
to actually parse the JSON you get back to see if everything went
according to plan...
Kind regards
Philipp Kern
