oops. scratch poopy.yml from the top-level On Mon, Sep 27, 2021 at 9:18 AM Guy Matz <guym...@gmail.com> wrote:
> 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! > ---------- Forwarded message --------- > From: Guy Matz <guym...@gmail.com> > Date: Wed, Sep 22, 2021 at 12:45 PM > Subject: organizing playbooks > To: <ansible-proj...@googlegroups.com> > > > 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 > <https://docs.ansible.com/ansible/2.8/user_guide/playbooks_best_practices.html#directory-layout> > ? That doesn't scale. Anyone have a better idea? > > Thanks!! > -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/CABnTgtX8cNvM6uPq_Rs0V7e8pk7L__03gaFoSBM62yMLe0bCkw%40mail.gmail.com.
