launching script file from URL with option defined directly in the job configuration

[Tudor Rogoz]

Hi 

I want to launch a rundeck job from the UI having the script from an URL, but the options defined directly in the job.

The problem is that rundeck doesn't recognize the option values and fails using the option key instead.

I'm using the @option.VARIABLE@ notation inside the script, and it worked fine when I was using inline script step instead of the URL step.Is this the normal behavior?

Thanks

Tudor

[Greg Schueler]

Hi Tudor,

Yes, the @option.VARIABLE@ syntax is only applied to inline scripts.  For URLs or local script files, the script is copied without modification.

You could still use the ${option.variable} syntax for arguments to the script, or environment variables if your sshd configuration allows it on the remote node.

I think ideally the @ syntax expansion should be a flag on the script step that you can enable or disable if you like.

--
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.