<h5 dir="auto">Issue Type:</h5>
<p dir="auto">Feature Idea</p>
<h5 dir="auto">Ansible Version:</h5>
<p dir="auto">ansible 1.5.4</p>
<h5 dir="auto">Environment:</h5>
<p dir="auto">Debian 7</p>
<h5 dir="auto">Summary:</h5>
<p dir="auto">Ability to use useradd's -o flag "allow to create users with duplicate (non-unique) UID"</p>
<h5 dir="auto">Steps To Reproduce:</h5>
<p dir="auto">not possible</p>
<h5 dir="auto">Expected Results:</h5>
<p dir="auto">This is useful if you want to create an ftp account with same permissions as another user but chroot  (with for example proftp's chroot ~ ) its home dir to a directory further down the tree, thus locking it out from alot of the main users directories but still have write access to its own home dir. (as both users share uid/gid both have write access)</p>
<h5 dir="auto">Actual Results:</h5>
<p dir="auto">not possible</p>
<p dir="auto">The recommended directory layout from the documentation (<a href="http://docs.ansible.com/ansible/playbooks_best_practices.html#directory-layout" rel="nofollow">http://docs.ansible.com/ansible/playbooks_best_practices.html#directory-layout</a>) indicates putting all playbooks at the top level, alongside inventory files. This can get really messy in a large project.</p>
<p dir="auto">We put all configuration in roles. Playbooks are basically mappings of a set of roles to a set of inventory. I believe that is best-practice to make roles reusable.</p>
<p dir="auto">In earlier Ansible versions (~ year ago?) it was possible to put playbooks in a subfolder and run them from the top folder (where inventory files are). Somewhere along the line that became impossible, because playbooks in a subfolder cannot see roles and group var files, in such case.</p>
<p dir="auto">Can we please get support for playbooks in subfolder? Why is that not a recommended best-practice in the documentation?</p>