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).
For Windows targets, use the win_command module instead.
-name:return motd to registered varcommand:cat /etc/motdregister:mymotd-name:Run the command if the specified file does not exist.command:/usr/bin/make_database.sh arg1 arg2 creates=/path/to/database# You can also use the 'args' form to provide the options.-name:This command will change the working directory to somedir/ and will only run when /path/to/database doesn't exist.command:/usr/bin/make_database.sh arg1 arg2args:chdir:somedir/creates:/path/to/database-name:safely use templated variable to run command. Always use the quote filter to avoid injection issues.command:cat{{myfile|quote}}register:myoutput
If you want to run a command through the shell (say you are using <, >, |, etc), you actually want the shell module instead. The command module is much more secure as it’s not affected by the user’s environment.
creates, removes, and chdir can be specified after the command. For instance, if you only want to run a command if a certain file does not exist, use this.
The executable parameter is removed since version 2.4. If you have a need for this parameter, use the shell module instead.
For Windows targets, use the win_command module instead.
This module is flagged as stableinterface which means that the maintainers for this module guarantee that no backward incompatible interface changes will be made.
For more information about Red Hat’s this support of this module, please
refer to this knowledge base article<https://access.redhat.com/articles/rhel-top-support-policies>