feat(diagnostics): ThreadDump deletion notification#1042
feat(diagnostics): ThreadDump deletion notification#1042andrewazores merged 4 commits intocryostatio:mainfrom
Conversation
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull Request blocked. webui submodule updates are performed automatically by CI when that repository is updated. Please revert or drop all changes to the webui submodule from this PR and perform any required frontend work by opening and merging a PR against cryostat-web.
There was a problem hiding this comment.
Pull Request blocked. webui submodule updates are performed automatically by CI when that repository is updated. Please revert or drop all changes to the webui submodule from this PR and perform any required frontend work by opening and merging a PR against cryostat-web.
andrewazores
force-pushed
the
thread-dump-delete-notification
branch
from
3db4a81 to
d037b3d
Compare
|
/build_test |
|
Workflow started at 9/8/2025, 4:32:37 PM. View Actions Run. |
|
No GraphQL schema changes detected. |
|
No OpenAPI schema changes detected. |
|
CI build and push: All tests pass ✅ |
|
@Josh-Matsuoka is the corresponding frontend PR cryostatio/cryostat-web#1802 also good to go? |
|
@andrewazores Yep, both look good to me. |
2 participants
Welcome to Cryostat! 👋
Before contributing, make sure you have:
mainbranch[chore, ci, docs, feat, fix, test]To recreate commits with GPG signature
git fetch upstream && git rebase --force --gpg-sign upstream/mainSee #894
Description of the change:
Adds a WebSocket notification emitted when a thread dump is successfully deleted.
Motivation for the change:
Mirrors how other resource deletions (ex. archived recordings, automated rules, stored credentials) are handled - the HTTP API responds with an HTTP 204, and there is also an accompanying WebSocket notification. The WebSocket notification allows all listening clients to update their local state reactively.