Is there a modern way of organizing playbooks? Are we still supposed to have our playbooks at the top level of the directory structure as described in The Playbooks Best Practices doc ? That doesn’t scale. Anyone have a better idea?
Thanks!!
Is there a modern way of organizing playbooks? Are we still supposed to have our playbooks at the top level of the directory structure as described in The Playbooks Best Practices doc ? That doesn’t scale. Anyone have a better idea?
Thanks!!
I posted the question below to the general ansible mailing list and no one got back to me! Very unlike the Ansible group . . .
So my question to the development group is: why can’t we have a playbooks directory at the same level as inventory, group_vars, role, etc? e.g.:
├── group_vars
│ ├── all
│ ├── nyc
│ ├── poopy
│ └── stoopy
├── host_vars
│ └── nyc-poopy-01
├── inventory
│ └── all
├── playbooks
│ ├── poopy
│ │ ├── main.yml
│ │ └── run_tasks_for_specific_group.yml
│ └── stoopy
│ ├── main.yml
│ └── run_specific_commands_that_rarely_get_run.yml
├── poopy.yml
└── roles
├── common
├── dbserver
└── webserver
Thanks!
oops. scratch poopy.yml from the top-level
Hi Matz
This should not have any issue, if you specify respective paths in config file.
We have playbooks, roles, global vars directories at the same level for few projects and there,
roles path is managed by ansible.cfg file.
Hope I understood your question correctly and the answer makes sense a bit.
Regards,
Nitesh