feat(dashboard): webhook rules status and test panel#83
Open
iceice400 wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
GET /api/webhooks/status— rule list, last-fired timestamps, engine state (no full URLs)POST /api/webhooks/test/{rule_name}— dummy POST withevent: testto verify connectivity from the PiWhy
Operators need visibility into webhook rules and a one-click way to verify LAN URLs without editing yaml or waiting for a real mesh event.
Depends on
PR #82 (webhook engine config). Merge #82 first, then rebase this branch onto
mainif needed.Type
Testing
python -m unittest tests.test_webhooks_routes tests.test_webhook_engine -v(13 tests, pass)Test plan
local.yaml, open Configuration → Advanced → Webhooksevent: testanddata.test: trueRelay / TX impact
None. Read-only status API + optional test POST; no pipeline changes beyond PR #82 engine tracking.
AI-assisted?
Implemented with AI assistance; unit tests run locally.