ansible.playbook package¶
Subpackages¶
Submodules¶
ansible.playbook.attribute module¶
- 
class 
ansible.playbook.attribute.Attribute(isa=None, private=False, default=None, required=False, listof=None, priority=0, class_type=None, always_post_validate=False)[source]¶ Bases:
object
ansible.playbook.base module¶
- 
class 
ansible.playbook.base.Base[source]¶ Bases:
object- 
DEPRECATED_ATTRIBUTES= ['sudo', 'sudo_user', 'sudo_pass', 'sudo_exe', 'sudo_flags', 'su', 'su_user', 'su_pass', 'su_exe', 'su_flags']¶ 
- 
load_data(ds, variable_manager=None, loader=None)[source]¶ walk the input datastructure and assign any values
- 
post_validate(templar)[source]¶ we can’t tell that everything is of the right type until we have all the variables. Run basic types (from isa) as well as any _post_validate_<foo> functions.
- 
 
ansible.playbook.become module¶
ansible.playbook.block module¶
- 
class 
ansible.playbook.block.Block(play=None, parent_block=None, role=None, task_include=None, use_handlers=False, implicit=False)[source]¶ Bases:
ansible.playbook.base.Base,ansible.playbook.become.Become,ansible.playbook.conditional.Conditional,ansible.playbook.taggable.Taggable- 
get_vars()[source]¶ Blocks do not store variables directly, however they may be a member of a role or task include which does, so return those if present.
- 
static 
load(data, play=None, parent_block=None, role=None, task_include=None, use_handlers=False, variable_manager=None, loader=None)[source]¶ 
- 
preprocess_data(ds)[source]¶ If a simple task is given, an implicit block for that single task is created, which goes in the main portion of the block
- 
serialize()[source]¶ Override of the default serialize method, since when we’re serializing a task we don’t want to include the attribute list of tasks.
- 
deserialize(data)[source]¶ Override of the default deserialize method, to match the above overridden serialize method
- 
 
ansible.playbook.conditional module¶
ansible.playbook.handler module¶
- 
class 
ansible.playbook.handler.Handler(block=None, role=None, task_include=None)[source]¶ Bases:
ansible.playbook.task.Task
ansible.playbook.handler_task_include module¶
- 
class 
ansible.playbook.handler_task_include.HandlerTaskInclude(block=None, role=None, task_include=None)[source]¶ Bases:
ansible.playbook.handler.Handler,ansible.playbook.task_include.TaskInclude
ansible.playbook.helpers module¶
- 
ansible.playbook.helpers.load_list_of_blocks(ds, play, parent_block=None, role=None, task_include=None, use_handlers=False, variable_manager=None, loader=None)[source]¶ Given a list of mixed task/block data (parsed from YAML), return a list of Block() objects, where implicit blocks are created for each bare Task.
ansible.playbook.included_file module¶
ansible.playbook.loop_control module¶
- 
class 
ansible.playbook.loop_control.LoopControl[source]¶ Bases:
ansible.playbook.base.Base
ansible.playbook.play module¶
- 
class 
ansible.playbook.play.Play[source]¶ Bases:
ansible.playbook.base.Base,ansible.playbook.taggable.Taggable,ansible.playbook.become.BecomeA play is a language feature that represents a list of roles and/or task/handler blocks to execute on a given set of hosts.
Usage:
Play.load(datastructure) -> Play Play.something(...)- 
compile_roles_handlers()[source]¶ Handles the role handler compilation step, returning a flat list of Handlers This is done for all roles in the Play.
- 
 
ansible.playbook.play_context module¶
- 
class 
ansible.playbook.play_context.PlayContext(play=None, options=None, passwords=None, connection_lockfd=None)[source]¶ Bases:
ansible.playbook.base.BaseThis class is used to consolidate the connection information for hosts in a play and child tasks, where the task may override some connection/authentication information.
- 
set_play(play)[source]¶ Configures this connection information instance with data from the play class.
- 
set_options(options)[source]¶ Configures this connection information instance with data from options specified by the user on the command line. These have a lower precedence than those set on the play or host.
- 
set_task_and_variable_override(task, variables, templar)[source]¶ Sets attributes from the task if they are set, which will override those from the play.
- 
 
ansible.playbook.playbook_include module¶
- 
class 
ansible.playbook.playbook_include.PlaybookInclude[source]¶ Bases:
ansible.playbook.base.Base,ansible.playbook.conditional.Conditional,ansible.playbook.taggable.Taggable
ansible.playbook.taggable module¶
ansible.playbook.task module¶
- 
class 
ansible.playbook.task.Task(block=None, role=None, task_include=None)[source]¶ Bases:
ansible.playbook.base.Base,ansible.playbook.conditional.Conditional,ansible.playbook.taggable.Taggable,ansible.playbook.become.BecomeA task is a language feature that represents a call to a module, with given arguments and other parameters. A handler is a subclass of a task.
Usage:
Task.load(datastructure) -> Task Task.something(...)- 
static 
load(data, block=None, role=None, task_include=None, variable_manager=None, loader=None)[source]¶ 
- 
preprocess_data(ds)[source]¶ tasks are especially complex arguments so need pre-processing. keep it short.
- 
static 
 
ansible.playbook.task_include module¶
- 
class 
ansible.playbook.task_include.TaskInclude(block=None, role=None, task_include=None)[source]¶ Bases:
ansible.playbook.task.TaskA task include is derived from a regular task to handle the special circumstances related to the - include: ... task.