Passing node attributes to the scripts

[Ben Gordon]

Hi,

Within a job I'm trying to run another job (subjob) and pass arguments.  It works fine when passing arguments like ${option.attribute}, but fails when passing arguments ${node.attribute}, e.g. -hostname ${node.username}.
If just prior to calling the subjob, I run a command "echo ${node.username}", it displays what I expect, the value from the resourcse.xml file against the node and the key "username".  However, when running the same command in the subjob, i.e. "echo ${node.username}", it displays "${node.username}".  It doesn't pass the value.  I have tried various alternatives, quotes, multiple quotes, @node.username@, etc, but to no avail.

Does anyone have a solution or is this a bug or by design?

Ben

[Greg Schueler]

Hi Ben,

Job references don't execute in a node context, so node attributes are not available for the arguments to the job. 

-- 

Greg

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

[Ben Gordon]

Hi Greg,

Thanks for your super quick reply.

So it is by design.  That is a pitty, it would be nice if it worked.

Ben

[Guido Bakker]

Hi Greg,

Is this something that will be implemented? Having job references in a node context would really simplify our job workflow.

Regards,

Guido

[Jason Hartnell]

Before the job reference is executed, shouldn't rundeck evaluate the variables being passed to the job reference?

This would be handy for building up a library of jobs that you may want to execute against specific nodes within parent workflow steps.

[Greg Schueler]

Hi All,

FYI: in Rundeck 1.6.1 we re-enabled the by-node functionality for Job References.  It is now an explicit flag to use this mode, since the default is to run the once in a workflow.  You can set a Job Reference to operate as a Node Step or Workflow Step.  (In jobs.xml this becomes nodeStep="true" in the <jobref> element)

When "Node Step" is checked for a Job Reference, it will not execute once per-node in the parent job.  You can pass the node attributes to the job reference in the argument string using ${node.name}, etc.

If you are migrating jobs from Rundeck 1.4 (where this was the default behavior for Job References), you should be able to do a simple find/replace on the jobs.xml output, before importing in 1.6.1. e.g:

perl -i.orig -lp -e 's/jobref /jobref nodeStep="true" /g' jobs.xml

--
Greg Schueler