A RFR ticket fedora-infrastructure#7563 was opened for a new micro-service named Message-Tagging-Service (aka MTS) to deploy in Fedora. It is a message-driven service triggered by MBS message to tag specific module build. That RFR ticket has detailed information for the service and requirement from module maintainers.

I was reminded that I need to open a ticket to ask for agreement on the proposal in the RFR ticket. This is the one. Currently, two things may be relative to rel-eng.

• MTS requires a rule file in order to find out which tags should be applied to a specific module build. Rule file is a yaml file, here is an example[1] and format explanation[2]. Once the RFR ticket is done through the process, I'm not sure if rel-eng could fill rules in the rule file and then maintain the rules updates.

• MTS should have a keytab to log into Koji and tag builds with proper permission. This is just like what MBS does currently to tag module build imported to Koji. The difference is after MTS is online, MBS will stop tagging, and MTS does that instead.

Thanks!

[1] https://github.com/fedora-modularity/message-tagging-service/blob/master/rules/mts-rules.yaml.
[2] https://pagure.io/modularity/blob/master/f/drafts/module-tagging-service/format.md