-
Notifications
You must be signed in to change notification settings - Fork 17
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
We need a method for the BZFE to signal the MEFE each time something relevant happens #13
Comments
Clarification: we do NOT want to capture events that happen solely in the BZFE and which can't be seen/refelected/displayed in the MEFE Example:
|
I highly recommend we design a system of messages based on AWS SNS. They are easy to subscribe to and work with. The best way in my opinion to trigger a lambda function to do something. I have been thinking how both the front end and back end could start relaying events to SNS for either to subscribe to. For example with unee-t/bugzilla-customisation#46 it's silly of me to poll |
@kaihendry I REALLY like the SNS idea. Each time a case is successfully updated, record(s) are added to the table 'bugs_activity' to log these changes. Maybe we can monitor this table and use the insert events into this table as a trigger to send the notifications we need?? |
|
as for unee-t/bugzilla-customisation#46 this should also be possible to have the MEFE use SNS to trigger the scripts we need... |
@kaihendry It seems that we could use a lambda function to do what we need to capture changes directly from the BZ database. Pre-requisite seem that we migrate from MariaDb to AWS Aurora which we probably want to test first but which does not seem that much of a stretch as Aurora is supposed to be fully compatible with MariaDb/MySQL... I appears to me that this could 'relatively' rapidly solve our notification issue in a rather elegant way... |
"Pre-requisite seem that we migrate from MariaDb to AWS Aurora " |
We can have a table in the BZ DB (Aurora - Unee-T Db schema v3.0) which is updated each time something changes in a case:
We 'just' need to have the relevant Lambda function’s ARN to finish implementing the SQL steps described there https://aws.amazon.com/blogs/database/capturing-data-changes-in-amazon-aurora-using-aws-lambda/ This will give us a way to have notification and use AWS to send these where we need these to go |
To summarize, the meteor back end server will receive Web hooks from a SNS Topic that a Lambda will publish to. The test lambda and what events it will be fed from the DB are detailed upon unee-t/bz-database#36 To get started, I suggest subscribing to arn:aws:sns:ap-southeast-1:812644853088:atest place holder. |
Closing this issue, since we have gone past the "need method" into implementation, e.g. #244 Though please refer to https://github.com/orgs/unee-t/projects/2 for an overview of the Notification project. |
As part of the MVP, we know that some interactions will be triggered in the Bugzilla Front End / BZFE first (the Unee-T dashboard).
The first thing we need to do is to send an alert to the relevant user(s) of the MEFE (email and/or SMS) each time a bug/case is updated in a product this MEFE user has been invited to.
We need to better understand how we can do that.
This is a show stopper: we can't have the BZFE user invite anyone to use the Unee-T MEFE (case.unee-t.com) without this.
@sebdeckers that'll be cool if you can have a go at this :-)
The text was updated successfully, but these errors were encountered: