From what I can tell, even if Greenwave gating is disabled, the Greenwave consumer will try to determine if a build on a decision update is a module build. These messages should just be ignored when Greenwave gating is disabled.

Also, the get_corresponding_module_build function gets called every time there is a decision update to see if the build is a module. This creates a Koji session every time which adds unnecessary load to MBS and Koji. One idea is to check if the subject type in the Greenwave message is redhat-module. There maybe other ways.

/cc @cqi