On Fri, Mar 6, 2015 at 11:47 AM, Craig White <[email protected]> wrote:
> given that I am a newbie, my opinions lack perspective. I think the > 'script' command should be able to be gathered from a template because > ansible is just a glorified shell script manager anyway and why keep it > emasculated? > Yikes! I would in no way say that ansible is just a glorified shell script manager. I do think you are lacking perspective > > I can run the script that is derived from the template and dropped on the > subject server with the shell command - I thought the script > 'creates/removes' functions added a bit of elegance that you don't get from > the shell module. > The shell and command modules also both utilize creates/removes In my non-humble opinion, I think templating a shell script or any script for that matter is pretty terrible. I'd recommend tempting a config that the script can utilize to gather the info it needs to perform a task, rather than building a script on the fly. Or allowing the script to run off of ENV vars, and passing an "environment" along with your command. -- Matt Martz @sivel sivel.net -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAD8N0v9N9LOF%3DrofQz6ahQV0ES9oBwYc_oKmfcO-y64Q%3D96i1w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
