-
Notifications
You must be signed in to change notification settings - Fork 15
Pass request to incident update actions #1497
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
Pass request to incident update actions #1497
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1497 +/- ##
==========================================
+ Coverage 79.49% 79.50% +0.01%
==========================================
Files 121 121
Lines 5417 5422 +5
==========================================
+ Hits 4306 4311 +5
Misses 1111 1111 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Nice, I like this. Small comment below.
@jladd-geant what do you want to add to this before marking it as ready? |
I will mark it as ready now, was just going over it again to see if I needed to do anything else first. |
I would have preferred sending a message outside of these helpers because then they can be reused in the API but that's probably not gonna happen. |
Well, we need some way to send a message from the helpers. Perhaps what we could do is to decouple "sending a message" from the |
b8132bb
to
b9aec97
Compare
|
Scope and purpose
Incident update actions currently dont have any good way to report errors to the UI beyond causing a 500 and can fail silently. This PR passes the request to bulk actions to allow for sending messages to UI when errors occur. geant-argus has bulk actions which interact with external services which can be much less obvious if broken. Also extra checks such as checking for a user's write permission before executing some actions which need to send messages to indicate insufficient permissions in the UI.
Contributor Checklist
Every pull request should have this checklist filled out, no matter how small it is.
More information about contributing to Argus can be found in the
Development docs.