Default value not referenced when using a multi-valued option.
Reported by Michael Gibson | 2012-08-27 14:41:47 UTC
- 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
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