Skip to content

Available TriggerActions

Jump to bottom
Konstantin Müller edited this page May 29, 2018 · 1 revision

System-Defined TriggerActions

The following TriggerActions are system-defined and are available out of the box without any special configuration.

NoopTriggerAction

Implementation class: no.mnemonic.services.triggers.action.NoopTriggerAction

Description: No-operation TriggerAction doing nothing except of logging the initParameters and triggerParameters during execution. Useful for testing when writing TriggerRules and no actual action should be performed.

Parameters: No parameters required.

HttpClientAction

Implementation class: no.mnemonic.services.triggers.action.HttpClientAction

Description: TriggerAction for calling HTTP(s) endpoints.

initParameters:

  • proxy: URL of a server which will be used to proxy requests (optional).

triggerParameters:

  • url: URL of the HTTP endpoint to call (required).
  • method: HTTP method to be used when making requests (optional, defaults to GET).
  • body: Body send in request (optional).
  • contentType: Media type of body data (optional, defaults to text/plain, ignored if body parameter is not specified).
  • Parameters starting with the prefix header@ will be sent as additional request headers (without the prefix).

Custom TriggerActions

Custom TriggerActions can be provided by implementing the no.mnemonic.services.triggers.action.TriggerAction interface and making the implementation class available of on the class path of the pipeline worker. Take a look at the interface definition for more details and the system-defined TriggerActions for implementation examples.

Clone this wiki locally