{"action":"opened","issue":{"url":"https://api.github.com/repos/fedora-infra/pdc-updater/issues/24","repository_url":"https://api.github.com/repos/fedora-infra/pdc-updater","labels_url":"https://api.github.com/repos/fedora-infra/pdc-updater/issues/24/labels{/name}","comments_url":"https://api.github.com/repos/fedora-infra/pdc-updater/issues/24/comments","events_url":"https://api.github.com/repos/fedora-infra/pdc-updater/issues/24/events","html_url":"https://github.com/fedora-infra/pdc-updater/issues/24","id":196763923,"number":24,"title":"Consumer's topic can't be constructed for internal message topics","user":{"login":"mprahl","id":11711106,"avatar_url":"https://avatars.githubusercontent.com/u/11711106?v=3","gravatar_id":"","url":"https://api.github.com/users/mprahl","html_url":"https://github.com/mprahl","followers_url":"https://api.github.com/users/mprahl/followers","following_url":"https://api.github.com/users/mprahl/following{/other_user}","gists_url":"https://api.github.com/users/mprahl/gists{/gist_id}","starred_url":"https://api.github.com/users/mprahl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mprahl/subscriptions","organizations_url":"https://api.github.com/users/mprahl/orgs","repos_url":"https://api.github.com/users/mprahl/repos","events_url":"https://api.github.com/users/mprahl/events{/privacy}","received_events_url":"https://api.github.com/users/mprahl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-20T19:48:24Z","updated_at":"2016-12-20T19:48:24Z","closed_at":null,"body":"To listen to Brew messages using STOMP internally, I've been using the topic `/queue/Consumer.pdc-updater-prod.VirtualTopic.eng.brew.build.tag`. The issue is that I can't tell the consumer in pdc-updater to listen on that topic based on how the topics are currently constructed in `consumer.py`.\r\n\r\nThis is how they are currently constructed:\r\n```\r\nself.topic = [\r\n    '.'.join([config['topic_prefix'], config['environment'], topic])\r\n    for handler in self.handlers for topic in handler.topic_suffixes\r\n]\r\n```\r\n\r\nSince the `topic_prefix` for the handler should be `/queue/Consumer.pdc-updater-prod.VirtualTopic.eng` and the `topic_suffix` is `brew.build.tag` (in #23), I am forced to provide an `environment` in the configuration even though the topic does not have one.\r\n\r\nI will gladly make the code changes necessary to support this, but I don't know what approach you'd like to take to address this.\r\n\r\nThank you for your help."}}
{"actor":{"display_login":"mprahl"}}