You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
_log.warning('No routing policy defined for "{t}" but routing_nitpicky is '
I am using the simplest form of tail message with the default fedmsg config
config = fedmsg.config.load_config()
for name, endpoint, topic, msg in fedmsg.tail_messages(topic='org.fedoraproject.prod.buildsys.build.state.change', mute=True, **config):
and my log is filled with: No routing policy defined for "org.fedoraproject.prod.buildsys.build.state.change" but routing_nitpicky is False so the message is being treated as authorized. on each koji message
which is quite useless imho. The default config is not to be nitpicky..
The text was updated successfully, but these errors were encountered:
@sidpremkumar I was able to disable this by editing the default config /etc/fedmsg.d/ssl.py and setting the value of validate_signatures to False.
And to disable the warning from code that calls tail_messages you have to slightly abuse fedmsg:
fedmsg/fedmsg/crypto/utils.py
Line 97 in c21d6b3
I am using the simplest form of tail message with the default fedmsg config
and my log is filled with:
No routing policy defined for "org.fedoraproject.prod.buildsys.build.state.change" but routing_nitpicky is False so the message is being treated as authorized.
on each koji messagewhich is quite useless imho. The default config is not to be nitpicky..
The text was updated successfully, but these errors were encountered: