Secure option values for sudo/ssh do not get passed to sub-jobs
-
HasanDefinitely +1.
I want to start a job, go do something else, and have it done when I return.
This way I have to keep checking when to start the next stage manually. It practically defeats my original interest in RunDeck.
-
Greg Schueler- Milestone order changed from 5 to 0
Design for this feature:
- When defining job references, the arguments will define which
values are passed along explicitly.
- If a job option is a "secure authentication" option, then the input must also be a "secure authentication" value, but can be a different one
- e.g if the args are "-suPassword ${option.databaseSuPassword}", then the secure authentication option "suPassword" is given the value of the original secure authentication option "databaseSuPassword"
- If a job option is a normal "secure" option, then the input must also be a secure option.
- secure options and "secure authentication" option values will never be mixed when passing to a job reference
- non-secure options will never be given the values of secure options.
-
Greg Schueler
(from [e29bfdb836ccf602630a9f134a53f33a9e36b92b]) Add documentation for secure option passing to job refs
[#524 Secure option values for sudo/ssh do not get passed to sub-jobs] https://github.com/dtolabs/rundeck/commit/e29bfdb836ccf602630a9f134...
-
Greg Schueler
(from [14db1072382df0a028ac6237e147e32a5e5b6d57]) add passing of sec auth options to job refs [#524 Secure option values for sudo/ssh do not get passed to sub-jobs]
segregate secure/auth/insecure option passing
https://github.com/dtolabs/rundeck/commit/14db1072382df0a028ac6237e... -
Greg Schueler
- State changed from new to needs_verification
-
Greg Schueler
- State changed from needs_verification to resolved
- Milestone order changed from 1 to 0
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.