More advanced options type for jobs

Skip to first unread message

Ben Kaplan

Feb 14, 2023, 7:08:55 AMFeb 14
to rundeck-discuss

We're searching for a way to have more advanced options/inputs to a job.
for example, 
- let's say we have "multi choose options" called "uid"
- each uid can have attributes related to it. let's call one of them "force_update" which is a boolean in this case.

So the options object should be more advanced than what Rundeck is offering at the moment and looks similar to the following structure:

  {"name": "uid", "value": "111", "attributes": {"name": "force_update", "value": true} }
  {"name": "uid", "value": "222", "attributes": {"name": "force_update", "value": false} }
  {"name": "uid", "value": "333", "attributes": {"name": "force_update", "value": true} }

And the UI should have a corresponding element for each attribute (in the case of a boolean probably a checkbox element) similar to the attached image.

1. We considering writing a plugin for this but is this even possible to add via a plugin? Maybe this is a UI plugin AND an Options plugin?
2. Any other way or ideas to achieve a similar outcome would be much appreciated



The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.


Feb 14, 2023, 7:29:27 AMFeb 14
to rundeck-discuss
Hi Ben,

The best approach for that is to create a own option plugin (based on this).

Currently Rundeck only admits this kind of format in the cascade or remote options JSON format.


Ben Kaplan

Feb 14, 2023, 8:35:48 AMFeb 14
Hey, thanks for the prompt reply!

But if Rundeck supports only this format for option, doesn't this means that any plugin we can write will always be required to adhere to this format?
If that is the case then we can't really change the default Option input without adding a more robust Option handling to the Rundeck core no?

We're trying to figure out if this use case is possible to do via plugins at all. Since the added attributes should appear in the UI as well probably this will require at least two plugins
1. extend option value
2. add UI elements to reflect the option's new structure.

Do you think this is possible to achieve only by adding external plugins?


You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To view this discussion on the web visit

Ben Kaplan

May 21, 2023, 3:19:45 PMMay 21
to rundeck-discuss

Reviving this thread to see if anyone can shed some light on the questions above regarding developing plugins to extend the Rundeck Job Options.
1. Can a plugin do what is described here? or is this a more low-level Rundeck Core code that needs to be changed?
2. If this is possible (to extend the option handling of a Rundek Job) and to also present the extended fields in the UI - is this a single plugin or two different plugins (options + UI)?


May 22, 2023, 12:55:58 PMMay 22
to rundeck-discuss
Hi Ben,

1. That would be possible using the custom plugin but...
2. Regarding the UI plugin it is possible but consider that Rundeck only understands the Name and Value format interface, take a look at this.

Getting the JSON values in an inline script through JQ to extract the desired values based on initial options values in your job is probably the best approach. 


Reply all
Reply to author
0 new messages