Skip to content

Commit

Permalink
precision for hook script stdout/stderr displayed as logs
Browse files Browse the repository at this point in the history
See also corresponding issue on main lsc project:
lsc-project/lsc#262
  • Loading branch information
David Coutadeur committed Jul 12, 2024
1 parent faaca8a commit 1939a17
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion source/syncrules.rst
Original file line number Diff line number Diff line change
Expand Up @@ -152,7 +152,7 @@ In this node, you can call a hook for each specific operations:
* ``deletePostHook``: path to the hook script managing each entry removal. The script will be called with 2 arguments: the DN of the entry, and the operation (``delete``). Nothing is passed on stdin.
* ``changeIdPostHook``: path to the hook script managing each entry renaming. The script will be called with 2 arguments: the DN of the entry, and the operation. The entry is passed on stdin, in the appropriate ``outputformat``

Hook scripts are not supposed to write anything to stdout or stderr. If so, LSC will display theses messages as log warnings.
Messages sent by the hook script on stdout are displayed as logs at level INFO. Messages sent by the hook script on stderr are displayed as logs at level ERROR.

Here is an example of modification in ldif, passed to stdin:

Expand Down

0 comments on commit 1939a17

Please sign in to comment.