Ummm, I'm not sure why you would want to do that really. I do have some suggestions...
Create roles, and set them up so that you can run either individual roles or sets of roles. For example I have a common role, a role to set up zabbix clients, a role to set up some things on the TSM servers and a role to set up things on ProLiant hardware. I can run one playbook that includes them all or I can run some playbooks that run specific sets of those. I generally prefer to run them all as that way I can make sure that nothing has changed. It takes a little bit longer, but it provides the assurance that someone hasn't modified the configuration manually. It sounds like you might want three main playbooks. One that runs everything, one that runs the standard configuration tasks and one that the developers can add to. I hope that this helps, Adam -- 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/a5b92453-1472-422e-9c62-5f38ce6ebebf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
