Licenses |
| ||||||||||||
Since |
|
Events can be used to listen to certain things happened in PIPEFORCE or in other systems. It’s also possible to trigger such events from inside a pipeline.
...
Event Key | Description | Payload | |||||
---|---|---|---|---|---|---|---|
| Fired every time a new property was created in the property store. | Contains as origin
| |||||
| Fired every time a property was copied in the property store. | Contains as origin the source property and as target the property where source was copied to.
| |||||
| Fired every time a property was deleted from the property store. | Contains as origin the property which was deleted and as target
| |||||
| Fired every time a property was moved from one key to another key. | Contains as origin the key of the source property and as target the key of the property where it was moved to.
| |||||
| Fired after a property has been updated in the property store. | Contains as origin the property before the update and as target the property after the update.
| |||||
| Fired after the hub service was successfully started and all setup scripts have been executed successfully. | This event contains no payload. | |||||
| Fired after the hub service was successfully started but right before all setup scripts will be executed. | This event contains no payload. | |||||
| Fired after the hub service was successfully started. | Contains as origin the configuration of the context as key-value-pairs. Target is
| |||||
| Fired every time a potential brute force attempt was detected. | ||||||
| Fired every time a login attempt has been failed. |