Creating projects

Projects are what we use to load playbooks into the Automation controller. This can be a file loaded on the controller filesystem or a Git repository. The controller will search for any valid playbook files in the project so that they can then be referenced by job templates. Project files should follow the standard playbook layout.

An important thing to keep in mind with projects and playbooks is not to try and create an all-encompassing project that contains every playbook or task file in a single project. There should be forethought and planning for how it is best to divide the playbooks. If everything goes into one project repository, it will eventually become too big to manage even as a team. This can lead to bloat, unused code, and cause issues when trying to remove one piece of the code, which leads to other things breaking.

This is also why collections and roles are important. Collections can contain modules and groups of roles in a cohesive unit. Separating...