Default value not referenced when using a multi-valued option.
Reported by Michael Gibson | August 27th, 2012 @ 02:41 PM
- Issue Type: Bug
- Rundeck version: 1.4.3
- JDK Version: Sun Java 1.6.0_31
- Server OS: CentOS 5.3
- Install type: Yum-rpm
Issue:
When using a multi-valued option the default value appears to be ignored.
Ex.
Option name: opt1
Default value: val5
Values list: val1,val2,val3,val4
Command: echo ${option.opt1}
Run job without specifying a value for the option.
Output: /bin/sh: ${option.opt1}: bad substitution
Looks like this may be somewhat similar to the behavior seen in
ticket #444?
http://rundeck.lighthouseapp.com/projects/59277/tickets/444-default...
Comments and changes to this ticket
-
AnnabellMitchell November 19th, 2020 @ 11:11 AM
There is no good and bad programmer in the industry. Here it all depends upon how that programmer adjusts to that project and how good he does that programming. As per bestessay review blog reviews their experience doesn`t count only the best coding programmer will get that project. Using your creative brain in developing that code is the only main thing to get success in that project.
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
Greg Schueler
Michael Gibson