You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would really nice to see what the response is from the "Trigger" button on the webhook creation screen. Currently it just says that the hook was sent, but it would be helpfull to show the response (HEADERS & Body) to be able to diagnose issues. Often the remote endpoint might fail, and seeing it's response makes debugging much easier.
For next level webhook help, see how GitHub does it under an Organisation Settings for Webhooks... they also keep a resent log of all the hooks, and allow replay. It would be cool to also show what Cockpit event triggered the WebHook to fire.
The text was updated successfully, but these errors were encountered:
Very nice. And very fast. It'll also be nice to see all the request parameters as sent from Cockpit too to help with debugging to ensure things are sent as you expected.
Cockpit now also displays the curl command for the request.
This shows all the parameters for the request + allows you to run the request in your cli. 🤝
It would really nice to see what the response is from the "Trigger" button on the webhook creation screen. Currently it just says that the hook was sent, but it would be helpfull to show the response (HEADERS & Body) to be able to diagnose issues. Often the remote endpoint might fail, and seeing it's response makes debugging much easier.
For next level webhook help, see how GitHub does it under an Organisation Settings for Webhooks... they also keep a resent log of all the hooks, and allow replay. It would be cool to also show what Cockpit event triggered the WebHook to fire.
The text was updated successfully, but these errors were encountered: