DJ> Why extra variables (-e) ignoring commands after pipeline ("|") while
DJ> running playbook with -e options.

http://docs.ansible.com/ansible/command_module.html says

  The command module takes the command name followed by a list of
  space-delimited arguments. The given command will be executed on all
  selected nodes. It will not be processed through the shell, so variables
  like $HOME and operations like "<", ">", "|", ";" and "&" will not work
  (use the shell module if you need these features).

So, you need the 'shell' module if you want to run a pipeline. (See
http://docs.ansible.com/ansible/shell_module.html#notes for some reasons
why you might not want to use 'shell' unless you really need to.)

                                      -Josh (j...@care.com)

(apologies for the automatic corporate disclaimer that follows)

This email is intended for the person(s) to whom it is addressed and may 
contain information that is PRIVILEGED or CONFIDENTIAL. Any unauthorized use, 
distribution, copying, or disclosure by any person other than the addressee(s) 
is strictly prohibited. If you have received this email in error, please notify 
the sender immediately by return email and delete the message and any 
attachments from your system.

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/22491.64838.961090.393963%40gargle.gargle.HOWL.
For more options, visit https://groups.google.com/d/optout.

Reply via email to