Add job option to have nodes default to un-checked
Reported by Andrew Crawford | November 10th, 2011 @ 05:44 PM
It would be useful to have a job option that causes the dispatch nodes to be unchecked by default, such that the job executor must enable the desired hosts at job runtime. This would allow node selection at runtime, without the risk of the job executor accidentally executing on all nodes defined in the job.
Comments and changes to this ticket
-
Ben Browning August 7th, 2012 @ 10:55 AM
We'd very much like this option too- we're implementing a multi-user environment with quick fixes (eg 'click here to try to restart $proprietary_service_foo') for issues, and it would be nice to be able to use the node filter to limit what hosts it can run on and then make the user check a box it should run on from that subset. Is there anything we can do to make this happen, or should we try to implement and submit a patch?
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
(DEPRECATED) Please use github issues for issue tracking at http://github.com/dtolabs/rundeck/issues
People watching this ticket
Andrew Crawford
Referenced by
-
484
Decouple Jobs from Workflows and Nodesets
Similar issues/requests: #70, #99, #185, #413, #414, #419...