A variable name can only include letters, numbers, and underscores. Not all strings are valid Ansible variable names. Variable precedence: Where should I put a variable? Transforming variables with Jinja2 filtersĭefining variables in included files and roles
Referencing key:value dictionary variables Once you understand the concepts and examples on this page, read about Ansible facts, which are variables you retrieve from remote systems.ĭefining variables as key:value dictionaries The ansible-examples github repository contains many examples of using variables in Ansible. You can also create variables during a playbook run by registering the return value or values of a task as a new variable.Īfter you create variables, either by defining them in a file, passing them at the command line, or registering the return value or values of a task as a new variable, you can use those variables in module arguments, in conditional “when” statements, in templates, and in loops. You can define these variables in your playbooks, in your inventory, in re-usable files or roles, or at the command line. To represent the variations among those different systems, you can create variables with standard YAML syntax, including lists and dictionaries.
With Ansible, you can execute tasks and playbooks on multiple different systems with a single command. Controlling how Ansible behaves: precedence rulesĪnsible uses variables to manage differences between systems.Virtualization and Containerization Guides.Controlling playbook execution: strategies and more.Executing playbooks for troubleshooting.Validating tasks: check mode and diff mode.Discovering variables: facts and magic variables.Variable precedence: Where should I put a variable?.Transforming variables with Jinja2 filters.When to quote variables (a YAML gotcha).Working with language-specific version managers.Controlling where tasks run: delegation and local actions.Understanding privilege escalation: become.
0 kommentar(er)
