...
- Document current unexpected behaviour of queryParameters.
- In a webhook definition:
- The queryParameters are always sent as a query string, regardless of whether GET or POST method is used. When using POST, only the rest of the values are sent in the body.
- When the Webhook specifies an existing REST Client: The
queryParametersspecified in the webhook definition are not passed to an existing restClient at all. The rest of the parameters (workspace, path, ...) are always sent as query string, regardless of whether we use POST or GET.
- In a webhook definition:
- Deprecate "queryParameters" property
- Introduce new "parameters" property.
- Only used when webhook defines a url. (Not used when webhook uses existing REST Client)
- Included in querystring when using GET.
- Included in body when using POST.
In Webhook YAML definition - Developer will be able add things to the context object.
...
- The webhook supplies the content node to the RestClient. (If it makes sense for the type of event. It does make sense for "publish" "unpublish" events.)
- It is available at "
context.content" in the RestClient, for example for usage in "defaultValues". - (Note: However the full content node is not auto-added to the querystring or body. But developer could add it to body if they want.)
Webhook body will include "uuid"
...