Support static webhook URLs for action endpoints that require dynamic identifiers

[jvgr019]

Currently, Kibana v 8.19 webhook connectors require a fixed URL configuration per connector. This creates a limitation when integrating with devlake API webhook beacuse closing incident has dynamic path parameters like issueKey .

Kibana doen't support dynamically constructing the webhook URL using values from the alert context or previous action output.

As a result, it is not possible to reliably implement a “create + close” workflow using only Kibana alert actions when the external API requires the issueKey identifier in the URL path.

Proposed improvement

• Allow both “create” and “close” operations to use a fixed webhook URL.
• Move all dynamic identifiers (e.g., issueKey) into the request body.

Workaround

At the moment, this limitation forces users to implement external middleware to store and correlate issueKey values between alert firing and recovery events.