Both of them have some commonalities but they solve different purposes. vars_files are read when the play starts. include_vars are read when the play reaches the task.<\/p>\n\n\n\n
Format
vars_files: directive
and
include_vars module <\/p><\/blockquote>\n\n\n\nvars_files:<\/strong>
vars_file directive can only be used when defining a play to specify variable files. The variables from those files are included in the playbook. Since it is used in the start of the play, it most likely implies that some other play(before this play) created those vars files or they were created statically before running the configuration; means they were kind of configuration variables for the play.<\/p>\n\n\n\ninclude_vars:<\/strong>
vars_files serves one purpose of including the vars from a set of files but it cannot handle the cases if<\/p>\n\n\n\n
- The vars files were created dynamically and you want to include them in play<\/li>
- include vars in a limited scope.<\/li>
- You have multiple vars files and you want to include them based on certain criteria e.g. if the local database exists then include configuration of local database otherwise include configuration of a remotely hosted database.<\/li>
- include_vars have higher priority than vars_files so, it can be used to override default configuration(vars).<\/li>
- include_vars are evaluated lazily(evaluated at the time when they are used).<\/li>
- You want to include vars dynamically using a loop.<\/li>
- You want to read a file and put all those variables in a named dictionary instead of reading all variables in the global variable namespace.<\/li>
- You want to include all files in a directory or some subset of files in a directory(based on prefix or exclusion list) without knowing the exact names of the vars file(s).<\/li><\/ul>\n\n\n\n
Ansible variable precedence<\/p>\n\n\n\n
Reference<\/strong>
Ansible variable precedence<\/p>\n\n\n\nReference<\/strong>
Ansible Variable Reference<\/a>
Ansible variable precedence<\/a><\/p>\n\n\n