... | ... | @@ -333,6 +333,16 @@ In exceptional cases, the hook executor may use a custom order for some specific |
|
|
|
|
|
In my opinion, we need to choose the exchange method for each callout point separately. We should assume as a good practice to always pass the context. We can prepare a generic controller to interrupt the hook loop used in callout points where the interruption is expected.
|
|
|
|
|
|
## Hook RESTAPI endpoint
|
|
|
|
|
|
REST API should be enhanced with the hook endpoint. It should allow a list of hooks and activate/deactivate selected ones.
|
|
|
|
|
|
Supported operations:
|
|
|
|
|
|
- `GET /hooks` - list the hooks
|
|
|
- `GET /hooks/{id}` - get the details about a specific hook, including the loading status with occurred errors
|
|
|
- `PUT /hooks/{id}` - edit hook, i.e., activate/deactivate hook (reload/unload), change the hook parameters
|
|
|
|
|
|
## Steps to implement hook
|
|
|
|
|
|
1. Look for needed callout points in the hook module
|
... | ... | |