Add support for multiple deployment tasks

[arcsector]

This might be something that is impractical, however I would definitely find it useful to be able to run multiple deployment tasks in list format. This would cut down on variable gathering (splunk boot, package, and other vars that main.yml collects) and it would allow people to centralize their playbooks more. Let me know if this makes sense or not. AFAIK, the changes that need to be made are mainly in the main.yml file and in any other references to the deployment_task.yml var. Is that correct?

[dtwersky]

@arcsector Not a bad idea, but this can cause some issues when the first task being executed changes something, which can cause the variables that are gathered in main.yml to be outdated when the next task runs.

If you have any suggestions how to avoid this, it sure can be implemented.

[arcsector]

Thanks for the notices, but I'd expect people to understand what they're doing enough to understand this distinction - maybe we can put a disclaimer in the README - This task changes variables that require a re-run of the main.yml task - do not chain any other tasks after this in your deployment task list or something like that. I could work on putting the list that would need that info together...

[BSonPosh]

I will second this request... it would very useful