Why set scenario only for the last item?

Also, this should check if user is not passing both scenario and result-id - same as for the REST API.

Why set scenario only for the last item?

It was actually the last (and only) appended item. I've changed the code to be more clear.

Also, this should check if user is not passing both scenario and result-id - same as for the REST API.

Added

Why not just do 'scenario': scenario in the dict above? Wouldn't passing "scenario": null to the REST API work?

Can you instead add another example, something from real data? Here are results with scenario set: https://taskotron.fedoraproject.org/resultsdb_api/api/v2.0/results?scenario:like=*

Updated

consider using dedent to have a cleaner indentation here.

This seems too long. PEP8 might fail. Could you move subject_identifier to the new line?

Just 2 tiny stylistic checks. Besides that it looks good +1
feel free to merge it once those are addressed.

Can you also update documentation under docs/? Looks like the examples are there listed too.

BTW, documenation is not auto-generated: https://docs.pagure.org/waiverdb/release-notes.html

For me, locally on Fedora 33, building documentation with tox -e docs also doesn't work - it's missing Python packages flask-migrate and stomp.py (dropping them into tox.ini fixes the issue).

This command should fail -- missing subject arguments.

Updated

Add test for this.

Looks good except a missing test for the new exceptional case.

Add test for this.

Added

+1