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
Copy file name to clipboardExpand all lines: docs/src/LIFECYCLE.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,7 +88,11 @@ As a result of a 'module discovery' process, the tasks for the execution of all
88
88
89
89
### Enabled script
90
90
91
-
A script or an executable file that returns the status of the module. The script has access to the module values in `$VALUES_PATH` and `$CONFIG_VALUES_PATH` files, more details about the values are available [here](VALUES.md#using-the-values-in-enabled-scripts). The variable `$MODULE_ENABLED_RESULT` passes the path to the file into which the script should write the module status: `true` or `false`.
91
+
A script or an executable file that returns the status of the module. The script has access to the module values in `$VALUES_PATH` and `$CONFIG_VALUES_PATH` files, more details about the values are available [here](VALUES.md#using-the-values-in-enabled-scripts).
92
+
93
+
The addon-operator exports two environment variables:
94
+
**`$MODULE_ENABLED_RESULT`** — *required* path to a temporary file; Write `true` or `false` here.
95
+
**`$MODULE_ENABLED_REASON`** — *optional* path to another file; write a **explanation** when the script decides to disable the module.
92
96
93
97
Below is an example of the `enabled` script that disables the module when parameter `param2` is set to "stopMePlease".
0 commit comments