A single level directory has a significant limitation, however, when the number of files increases or when the system has more than one user. In it, all files are contained in the same directory which makes it easy to support and understand. j2 files/ # bar.txt # <- files for use with the copy resource foo.sh # <- script files for use with the script resource vars/ # main.yml # <- variables associated with this role defaults/ # main.yml # <- default lower priority variables for this role meta/ # main. The single-level directory is the simplest directory structure. Production # inventory file for production servers staging # inventory file for staging environment group_vars/ group1 # here we assign variables to particular groups group2 # "" host_vars/ hostname1 # if systems need specific variables, put them here hostname2 # "" library/ # if any custom modules, put them here (optional) module_utils/ # if any custom module_utils to support modules, put them here (optional) filter_plugins/ # if any custom filter plugins, put them here (optional) site.yml # master playbook webservers.yml # playbook for webserver tier dbservers.yml # playbook for dbserver tier roles/ common/ # this hierarchy represents a "role" tasks/ # main.yml # <- tasks file can include smaller files if warranted handlers/ # main.yml # <- handlers file templates/ # <- files for use with the template resource 2 # <- templates end in.
0 kommentar(er)
