-
Notifications
You must be signed in to change notification settings - Fork 31
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
Backend state changes #470
Backend state changes #470
Conversation
src/main/java/io/cryostat/net/web/http/api/v1/RecordingDeleteHandler.java
Show resolved
Hide resolved
Looks good otherwise! Thanks for taking this on. |
src/main/java/io/cryostat/net/web/http/api/v1/RecordingsPostHandler.java
Outdated
Show resolved
Hide resolved
src/main/java/io/cryostat/net/web/http/api/v1/TargetRecordingDeleteHandler.java
Outdated
Show resolved
Hide resolved
…otification category
@Josh-Matsuoka do you have any interest in looking at cryostatio/cryostat-web#165 ? That's the corresponding frontend issue. This would simply entail adding notification handlers for each of these new notification types emitted and either using the notification payload to update the view, or if that's infeasible then to use the notification as a trigger to poll for fresh data. |
I can take a look at that, sure |
Hi,
This PR addresses cryostatio/cryostat#354 , sending events on the Notification channel when recordings are created/deleted, archived, and templates are uploaded/deleted. I've adjusted the tests accordingly.