My understanding is that with the planned retirement of the PDC:
https://lists.fedoraproject.org/archives/list/[email protected]/thread/JHKHWYU5XK7H2P2QZZCCQR4ZRCTY3OSB/ Querying for module information should be done using the MBS and/or Koji APIs. Various code that I maintain (in OSBS, fedmod, and random tooling) wants to do module build lookups - different variations of "look up the modulemd for latest build of a NAME:STREAM[:VERSION]". Variations generally being exactly what "latest" means here. The code generally already is using Koji and the MBS api is quite limited, so I've chosen to do the lookups via Koji. https://fishsoup.net/misc/get-module-builds Is a test tool that incorporates most of the capability that I needed across my uses. It's distinctly more than a couple of lines of code - I can cut-and-paste it for now, but what's the right long-term home? Is there a simpler way? My best idea right now is that if the 'base_version' and'status' part of my code was simplified to simply be "tag" and avoid reliance on the tag structure of Fedora, then this might make a reasonable addition to the Koji CLI and API - there are some things that using raw tags for the query makes trickier, but it's probably workable. Thanks for any input! Owen
_______________________________________________ infrastructure mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]/message/C7PZPQVRKLQ3PPKD726YR5K2EMYQUZQ5/
