This shows you the differences between two versions of the page.

Link to this comparison view

muster:8.0:custom_actions [2018/01/11 08:21] (current)
Line 1: Line 1:
 +===== Handling custom actions ======
 +Muster custom actions can be spawned by the Dispatcher or the Render clients, depending if they are jobs based or chunk based.
 +In both scenarios, you can pass arguments to an action using the template %ATTR substitution syntax. I.e. if you want to pass a job ID to a custom action you could write something like:
 +Alternatively,​ Muster exports a custom environment within each action, with the following keys available:
 +You can query those values, directly inside your action code, using getenv or whatever command your script/​language supports.
  • muster/8.0/custom_actions.txt
  • Last modified: 2018/01/11 08:21
  • (external edit)