@@ -72,11 +72,11 @@ every time a ``box.status`` system event is broadcasted, or after the ``apply``
72
72
If multiple custom roles have the ``on_event `` callback defined, these callbacks are called one after another in the order
73
73
defined by roles dependencies.
74
74
75
- The ``on_event `` callback provides 3 arguments, when it is called:
75
+ The ``on_event `` callback returns 3 arguments, when it is called:
76
76
77
77
- ``config ``, which contains the configuration of the role;
78
78
79
- - ``key ``, which reflects the trigger event:
79
+ - ``key ``, which reflects the trigger event and is set to :
80
80
81
81
- ``config.apply `` if the callback was triggered by a configuration update;
82
82
@@ -87,11 +87,11 @@ If the callback is triggered by a configuration update, the ``value`` shows the
87
87
88
88
.. NOTE ::
89
89
90
- - All ``on_event `` callbacks with the ``config.apply `` key are executed as a part of the configuration process.
91
- Process statuses ``ready `` or ``check_warnings `` are reached only after all such ``on_event `` callbacks are done.
90
+ - All ``on_event `` callbacks with the ``config.apply `` key are executed as a part of the configuration process.
91
+ Process statuses ``ready `` or ``check_warnings `` are reached only after all such ``on_event `` callbacks are done.
92
92
93
- - All ``on_event `` callbacks are executed inside of a ``pcall ``. If an error is raised for a callback, it is logged
94
- with the ``error `` level and the series execution continues.
93
+ - All ``on_event `` callbacks are executed inside of a ``pcall ``. If an error is raised for a callback,
94
+ it is logged with the ``error `` level and the series execution continues.
95
95
96
96
Creating a custom role includes the following steps:
97
97
0 commit comments