From de851ce5b08343f62fc8b8ea7f44005f286e567e Mon Sep 17 00:00:00 2001 From: Luiz Carvalho Date: Nov 07 2018 14:11:54 +0000 Subject: Undeprecate subject param for decision endpoint The subject parameter for the decision endpoint is still heavily used by Bodhi. It is done so because the subject parameter allows clients to perform a single request to check the decision of various subjects. Fixes #329 Signed-off-by: Luiz Carvalho --- diff --git a/greenwave/api_v1.py b/greenwave/api_v1.py index dea968d..19e5c7f 100644 --- a/greenwave/api_v1.py +++ b/greenwave/api_v1.py @@ -281,7 +281,12 @@ def make_decision(): artefact we are making a decision about. The meaning of the identifier depends on the subject type. See :ref:`subject-types` for details of how each subject type is identified. - :jsonparam list subject: *Deprecated:* Pass 'subject_type' and 'subject_identifier' instead. + :jsonparam list subject: A list of items about which the caller is requesting a decision + used for querying ResultsDB and WaiverDB. Each item contains one or more key-value pairs + of 'data' key in ResultsDB API. + For example, [{"type": "koji_build", "item": "xscreensaver-5.37-3.fc27"}]. + Use this for requesting decisions on multiple subjects at once. If used subject_type and + subject_identifier are ignored. :jsonparam bool verbose: A flag to return additional information. :jsonparam list ignore_result: A list of result ids that will be ignored when making the decision.