-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DITAA diagram for bugyou #1
base: develop
Are you sure you want to change the base?
Conversation
Misses the point that consumes messages from fedmsg. |
+-------------------------------------------------------------------------------------------+ | ||
| | | ||
| Plugins listen to the assigned queue and | | ||
| consumes the messages and pushes the messages to the issue tracking tools | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Proposal: Plugins listen to their own queue, consumes the messages as they are sent and pushes the messages (the message or something else? -- Alternative: report the issue from the message) to the configured issue tracking tools
The diagram looks good, the only part which I isn't really clear to me is the feedback loop at the bottom from the plugins to the message filter via redis. |
@@ -1,29 +1,46 @@ | |||
Bugyou Controller(bugyou-plugins) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You may want to drop the -
as ditaa seems to have issues with it (check the png)
LGTM! |
No description provided.