Krikri::Play

Every roles: entry's own defaults/main.yml and vars/main.yml, merged in role order (a later role wins a name collision), kept as two separate layers because real Ansible ranks them either side of play vars:.

Real Ansible loads ALL of a play's roles - and their vars/defaults

• into the variable manager when the play is SET UP, not when each role's tasks reach the front of the queue, so a role can see the vars of a role that runs AFTER it. Verified against ansible-core 2.19.4 (roles: [alpha, beta], names defined only in beta: only_beta_var is defined inside alpha is True). This engine scoped them to the owning role and its dependents, so such a reference resolved to nothing - which is what made geerlingguy.php's own when: php_packages is not defined run a task real Ansible skips (php_packages lives in buluma.php/vars/main.yml, a role that runs later in the same dependency chain).

Every roles: entry's own defaults/main.yml and vars/main.yml, merged in role order (a later role wins a name collision), kept as two separate layers because real Ansible ranks them either side of play vars:.

Real Ansible loads ALL of a play's roles - and their vars/defaults

• into the variable manager when the play is SET UP, not when each role's tasks reach the front of the queue, so a role can see the vars of a role that runs AFTER it. Verified against ansible-core 2.19.4 (roles: [alpha, beta], names defined only in beta: only_beta_var is defined inside alpha is True). This engine scoped them to the owning role and its dependents, so such a reference resolved to nothing - which is what made geerlingguy.php's own when: php_packages is not defined run a task real Ansible skips (php_packages lives in buluma.php/vars/main.yml, a role that runs later in the same dependency chain).

debugger: at play scope - always/never/on_failed/on_skipped/ on_unreachable. A task's own debugger: wins.

debugger: at play scope - always/never/on_failed/on_skipped/ on_unreachable. A task's own debugger: wins.

force_handlers: true play keyword - run notified handlers even when a task failed on the host, exactly like the --force-handlers CLI flag (real Ansible honors both).

force_handlers: true play keyword - run notified handlers even when a task failed on the host, exactly like the --force-handlers CLI flag (real Ansible honors both).

Whether the play actually wrote a gather_facts: key, as opposed to defaulting to true. Only --gathering explicit needs the distinction: under it, facts are gathered solely for plays that asked in so many words, so "unset" and "explicitly true" cannot be conflated.

Whether the play actually wrote a gather_facts: key, as opposed to defaulting to true. Only --gathering explicit needs the distinction: under it, facts are gathered solely for plays that asked in so many words, so "unset" and "explicitly true" cannot be conflated.

gather_subset: - which fact families the implicit fact gathering collects (all, min, network, hardware, mounts, and !negations).

gather_subset: - which fact families the implicit fact gathering collects (all, min, network, hardware, mounts, and !negations).

gather_timeout: / fact_path: - real play keywords feeding the implicit setup call: per-family fact-collection timeout in seconds (real default 10) and the directory *.fact custom facts are gathered into ansible_local from (real default /etc/ansible/facts.d).

gather_timeout: / fact_path: - real play keywords feeding the implicit setup call: per-family fact-collection timeout in seconds (real default 10) and the directory *.fact custom facts are gathered into ansible_local from (real default /etc/ansible/facts.d).

any_errors_fatal: - one host failing aborts the play for ALL of them. max_fail_percentage: - abort once the share of failed hosts is STRICTLY GREATER than this (verified: 1 of 3 hosts, i.e. 33.3%, aborts at 33 but not at 34; 0 aborts on any failure; 100 never does). Both are per serial: batch. module_defaults: - per-module default arguments, keyed by module name. Applies at play, block and task scope, nearest wins, and an argument the task sets itself always wins over a default.

any_errors_fatal: - one host failing aborts the play for ALL of them. max_fail_percentage: - abort once the share of failed hosts is STRICTLY GREATER than this (verified: 1 of 3 hosts, i.e. 33.3%, aborts at 33 but not at 34; 0 aborts on any failure; 100 never does). Both are per serial: batch. module_defaults: - per-module default arguments, keyed by module name. Applies at play, block and task scope, nearest wins, and an argument the task sets itself always wins over a default.

order: - the order hosts are processed in: inventory (default), reverse_inventory, sorted, reverse_sorted, shuffle.

order: - the order hosts are processed in: inventory (default), reverse_inventory, sorted, reverse_sorted, shuffle.

remote_user: at play scope - the connection user, i.e. what ansible_user would say. A task's own remote_user: wins over it.

remote_user: at play scope - the connection user, i.e. what ansible_user would say. A task's own remote_user: wins over it.

serial: - raw batch tokens, each either a count ("2") or a percentage ("50%"). Empty means the play runs against every host at once, which is what this engine always did.

serial: - raw batch tokens, each either a count ("2") or a percentage ("50%"). Empty means the play runs against every host at once, which is what this engine always did.

strategy: - linear (default) runs every host through a task before any starts the next; free lets each host run the whole task list independently.

strategy: - linear (default) runs every host through a task before any starts the next; free lets each host run the whole task list independently.

Appends a short String representation of this object which includes its class name and its object address.

class Person
  def initialize(@name : String, @age : Int32)
  end
end

Person.new("John", 32).to_s # => #<Person:0x10a199f20>

vars_files: - each entry is the list of candidate paths for one slot: a plain entry is a one-element list, a nested list is "first of these that exists". Paths may be templated, including against facts, so they are resolved per host at run time.

vars_files: - each entry is the list of candidate paths for one slot: a plain entry is a one-element list, a nested list is "first of these that exists". Paths may be templated, including against facts, so they are resolved per host at run time.

vars_prompt: - name/prompt/private/default per entry, asked before the play runs.

vars_prompt: - name/prompt/private/default per entry, asked before the play runs.