taskotron / resultsdb

#35 Make UUID useable as job_id in all the resultsdb_api searches
Closed: Fixed Opened by jskladan.

Closed: Fixed
Reopen Issue

At the moment, the resultsdb ony accepts UUID in place of job_id in the job-search /.../jobs/{uuid}. Make sure to support UUID instead of job_id in all reasonable places. As long as the UUID is not required to actually be unique in the DB, this only applies to GET calls.

This ticket had assigned some Differential requests:
D448
Metadata
None
None
None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.