Issue when Using Cascading Remote Options

[David Petzel]

I'm trying to leverage Cascading remote options and running into a bit of trouble. I've gotten the options defined, and the endpoints configured so I am able to select option1, and option2 values are correctly filtered to just the items I want. All good so far.

However if I then want to use those options in command line argument its not working.

If I use the syntax of "${option.MyOptionName.value}", the script will get invoked, however the value of the variable is not resolved, and instead that literal string is passed through

If I use the syntax that is listed on the bottom of the page when you create the option ("${option.preserve_templates}"), the script won't even run. Even with debug logging on, it doesnt seem very useful. sanitized output here: https://gist.github.com/dpetzel/5732361

I'm pretty sure the rest of the job is configured properly, as it it RUNS (logs into the remote node and echos the string I told it to), using the first syntax, however it doesn't resolve the variable value, so I can get it to run or fail, but just changing the way I access the option.

Any idea?

[Greg Schueler]

can you post your job.xml?

--
Greg Schueler

--
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 rundeck-discu...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[David Petzel]

On Fri, Jun 7, 2013 at 5:06 PM, Greg Schueler <gr...@dtosolutions.com> wrote:

can you post your job.xml?

Just pasted the job xml in the comment on the gist: https://gist.github.com/dpetzel/5732361 

Thanks

[NublaII Lists]

I know this is old, but I believe this is the same problem I reported here: https://github.com/rundeck/rundeck/issues/6972

It makes cascading options unusable with api-executed jobs.