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
{{ message }}
This repository was archived by the owner on Aug 29, 2023. It is now read-only.
We use a word "ticket" for a task in the context of "dastracker" and the word "task"
91
-
in the context of the external task trackers.
98
+
- Ticket - an issue in the context of "dastracker"
99
+
- Task - an issue in the context of the end task tracker.
100
+
- Subscription - a webhook or polling, for retrieving updates from the end task tracker.
92
101
93
102
### Plugin development
94
103
The functionality of dastracker might be extended by using plugins. Each plugin is an independent process/container,
95
104
implementing [Go RPC server](https://pkg.go.dev/net/rpc). Each exported method of the plugin handler must have a signature of `func(req lib.Request, res *lib.Response)`,
96
105
these methods might be referred and called in the configuration.
97
106
98
-
Also, the `lib.Plugin` structure has a field, named `SetUpTrigger` with signature of `func(req SetUpTriggerReq, resp *SetUpTriggerResp) error`.
99
-
This field might be filled in order to allow hanging on some triggers in the configuration file.
100
-
If no method is provided, dastracker will do nothing on any trigger, hanged on the plugin.
107
+
Plugin may provide methods to subscribe and unsubscribe from events, for that, plugin should implement interface:
0 commit comments