An Ansible task is a named YAML list item that invokes one module with its arguments on managed hosts. Put tasks under a play’s tasks: key, write them in the order they should run, and use fully qualified collection names such as ansible.builtin.copy or ansible.builtin.package. Variables, loops, conditions, registered results, and handlers let the same task describe safe, repeatable automation instead of a one-off command.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
This guide shows the syntax, execution model, reusable patterns, validation commands, and failure fixes you need to define reliable tasks.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Where tasks fit in a playbook
A playbook is a YAML document containing one or more plays. A play maps a group of hosts to an ordered set of tasks. The play’s hosts value selects the inventory group, while tasks contains the actions Ansible performs on those hosts.
Each task normally calls exactly one Ansible module. The module supplies the operation’s semantics—creating a directory, copying a file, installing a package, or managing a service—while the task’s name explains the intended result. Tasks run from top to bottom by default.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
Minimal playbook
- name: Configure web servers
hosts: web
tasks:
- name: Ensure the application directory exists
ansible.builtin.file:
path: /opt/myapp
state: directory
mode: '0755'The item beginning with - name is the task. ansible.builtin.file is the module, and the indented keys are its arguments. The play can contain any number of tasks after this item.
Anatomy of a task
| Part | Purpose | Example |
|---|---|---|
| Task name | A readable description shown in run output | Ensure the application directory exists |
| Module key | Selects the operation; prefer a fully qualified collection name | ansible.builtin.file |
| Module arguments | YAML parameters that define the desired state | path, state, mode |
| Task keywords | Controls such as when, loop, register, and notify |
when: ... |
Use names specific enough that a run tells you what was checked or changed. “Do setup” is less useful than “Install required packages” because the latter identifies the outcome without opening the file.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsDefine a task step by step
1. Choose a purpose-built module
Start by identifying the state you want, then select the module designed for it. Common choices include:
ansible.builtin.filefor files, directories, ownership, permissions, and links.ansible.builtin.copyfor placing a known local file on the managed host.ansible.builtin.templatefor rendering a Jinja2 template with variables.ansible.builtin.packagefor installing or removing packages through the host’s package manager.ansible.builtin.servicefor starting, stopping, enabling, or restarting services.ansible.builtin.debugfor displaying a value or message while developing a play.
Purpose-built modules generally express idempotent intent: running the task again should leave an already-correct system unchanged. Use ansible.builtin.command or ansible.builtin.shell only when no suitable module provides the operation. A shell command describes a procedure, so you may need additional conditions to prevent it from running unnecessarily.
2. Add arguments as YAML
Place module parameters directly below the module key at the next indentation level. YAML indentation is significant; tabs and misaligned keys can turn a valid-looking file into a syntax error or a different data structure.
- name: Install the web package
ansible.builtin.package:
name: nginx
state: presentQuote values when YAML’s type conversion could surprise you. File modes are the classic case: write mode: '0644' rather than an unquoted value so the module receives the intended permission string. Quote a value that begins with special YAML characters or contains a Jinja expression whose type must remain a string.
Free tools Windows power users keep installed
One-click scans. No signup required.
3. Use variables for differences
Hard-coded values make a task difficult to reuse across environments. Define values in play variables, inventory, reusable task files, roles, or the command line, then reference them with Jinja2 expressions in module arguments.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
- name: Create the application directory
ansible.builtin.file:
path: '{{ app_directory }}'
state: directory
mode: '0755'Keep the variable’s meaning clear. A variable named app_directory communicates more than a generic name such as path. If a value is optional, establish a deliberate default rather than allowing an undefined-variable error halfway through a run.
4. Register a result when a later task needs it
Add register to save a module’s return data under a variable. Later tasks can inspect that data in a condition, display it, or use it to shape another operation.
- name: Check whether the marker exists
ansible.builtin.stat:
path: /opt/myapp/ready
register: marker
- name: Report the marker state
ansible.builtin.debug:
msg: 'Marker exists: {{ marker.stat.exists }}'Registered data is especially useful when a subsequent action depends on what the first task discovered. Give the result a descriptive name and inspect the module documentation for the return fields it provides.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →5. Repeat one task with a loop
Use loop when the same operation applies to multiple items. The current item is available as {{ item }} by default.
- name: Install utility packages
ansible.builtin.package:
name: '{{ item }}'
state: present
loop:
- curl
- jqKeep loop data homogeneous: each item should have the shape the module arguments expect. For structured items, use fields such as {{ item.name }} and {{ item.state }}. If nested loops or included files make item ambiguous, set a deliberate loop variable with loop_control and reference that name instead.
6. Gate execution with when
A when clause is a raw Jinja2 expression. Do not wrap it in {{ }}.
- name: Install the Red Hat package
ansible.builtin.package:
name: httpd
state: present
when: ansible_facts['os_family'] == 'RedHat'When a task has both loop and when, Ansible evaluates the condition separately for each item. This lets one task skip only the items that do not qualify. Conditions can test variables, facts, registered results, or several expressions joined with normal Jinja2 and Python-style operators.
Recommended Free Tools
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
7. Notify follow-up work only after a change
Configuration changes often require a service reload or restart. Add notify to the task that changes the configuration, then define a handler with the matching name.
- name: Render application configuration
ansible.builtin.template:
src: app.conf.j2
dest: /etc/myapp/app.conf
mode: '0644'
notify: Restart application
handlers:
- name: Restart application
ansible.builtin.service:
name: myapp
state: restartedA handler is a special task that runs when notified by a task reporting changed. If the template is identical to the existing file, the task is normally ok and the restart is not triggered. The handler name must match the notification exactly.
Module tasks versus command tasks
| Pattern | Use it when | Trade-off |
|---|---|---|
| Purpose-built module | An Ansible module models the desired resource | Clear intent and usually safer repeatability |
ansible.builtin.command |
A program must be invoked without shell features and no module fits | Procedure is explicit, but idempotence may require your own checks |
ansible.builtin.shell |
Shell operators, pipes, expansion, or redirection are genuinely required | Most opaque; quoting, portability, and repeat-run behavior need extra care |
Do not replace a module with a shell command merely because the command is familiar. A package command, file permission command, or service restart usually has a module that can report whether the requested state is already satisfied.
Variables and the templating boundary
Jinja2 expressions substitute values inside task arguments, for example dest: '{{ config_path }}'. Templates can contain Jinja2 loops and conditionals to render file content. That templating syntax does not generate new playbook task items. The playbook itself remains machine-parseable YAML, and task repetition belongs in a task-level loop.
Keep the boundary clear:
- Use a task loop when the same module action must run for several items.
- Use a Jinja2 loop inside a template when one file should contain repeated rendered content.
- Use a
whenexpression to decide whether a task runs, not to manufacture YAML tasks.
Mixing these responsibilities makes troubleshooting harder because a template error and a playbook-structure error occur at different stages.
Combining loop, when, variables, and handlers
The following play demonstrates the common controls in one coherent play. It installs a variable list of packages, renders a configuration using a variable destination, reports that destination only on Red Hat systems, and restarts the service only when the rendered file changes.
- name: Deploy application configuration
hosts: app
vars:
config_path: /etc/myapp/app.conf
packages:
- curl
- jq
tasks:
- name: Install required packages
ansible.builtin.package:
name: '{{ item }}'
state: present
loop: '{{ packages }}'
register: package_results
- name: Render application configuration
ansible.builtin.template:
src: app.conf.j2
dest: '{{ config_path }}'
mode: '0644'
notify: Restart application
- name: Report configuration path on Red Hat systems
ansible.builtin.debug:
msg: 'Configuration is at {{ config_path }}'
when: ansible_facts['os_family'] == 'RedHat'
handlers:
- name: Restart application
ansible.builtin.service:
name: myapp
state: restartedIn this example, packages supplies the loop data, item supplies each package name, and package_results stores the loop task’s result for later use if needed. The condition is evaluated against each host, while the handler is queued only if the template task reports a change.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
Execution order and host behavior
Ansible normally applies the current task to all hosts matched by the play before moving to the next task. Therefore, a play with tasks A, B, and C does not complete A, B, and C on the first host before starting A on the second; it advances task by task across the matched hosts according to the play’s execution settings.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteTasks proceed from top to bottom unless a conditional skips one, a failure stops processing for a host, or another playbook control changes the normal flow. By default, a host that fails is removed from the remaining tasks in that play, while other hosts may continue. Read the recap to see which hosts were ok, changed, skipped, or failed.
Ordering matters when one task creates a prerequisite for the next. Put directory creation before file placement, package installation before service management, and configuration rendering before a notification that depends on the new configuration.
Reuse tasks with imports and includes
As a play grows, move related task items into separate files and bring them into a play. A static import_tasks is expanded when Ansible parses the playbook, while a dynamic include_tasks is selected during execution. That timing affects conditionals and loops applied to the file:
| Choice | Expansion time | Useful when |
|---|---|---|
import_tasks |
Parse time | The set of tasks is known up front and should be visible to static analysis and listing |
include_tasks |
Run time | The file to include depends on variables, facts, or a per-item decision |
Both mechanisms reuse ordinary task definitions; they do not change the syntax of the tasks inside the file. Keep included files focused and give every task a useful name so listings and failure messages remain understandable.
Validate before changing hosts
Use Ansible’s built-in inspection options before a real run. The exact preview behavior depends on the installed Ansible version and on whether each module supports the requested mode.
| Command | What it checks or shows |
|---|---|
ansible-playbook site.yml --syntax-check |
Parses the playbook and reports YAML or playbook-structure errors without running tasks |
ansible-playbook site.yml --list-hosts |
Shows the hosts selected by the plays |
ansible-playbook site.yml --list-tasks |
Lists the tasks Ansible selected for the run |
ansible-playbook site.yml --check |
Requests a dry-run preview from modules that support check mode |
ansible-playbook site.yml --check --diff |
Requests the check-mode preview plus textual differences for modules that support diff output |
Run syntax checking first; it catches structural mistakes before inventory or remote access becomes part of the problem. Use --list-hosts to verify that the intended inventory group is targeted and --list-tasks to confirm that a conditional or imported file is being selected as expected.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Check and diff modes are previews, not guarantees. A module may lack check-mode support, may not be able to predict a change exactly, or may omit sensitive differences. Treat the result as an aid to review, then test against an appropriate host before broad deployment.
Common task-definition problems and fixes
The module name is ambiguous
Short names can resolve differently when multiple collections provide similarly named modules. Use the FQCN, such as ansible.builtin.file, throughout modern playbooks. This makes the selected implementation clear and follows the official guidance for Ansible 2.10 and later.
The task is skipped unexpectedly
Read the rendered condition and the host facts. Confirm that the variable exists, that the fact key is spelled correctly, and that the when value is a raw expression rather than a quoted {{ }} expression. With a loop, inspect which item failed the condition instead of assuming the entire task was skipped.
The task reports changed every run
Prefer a purpose-built idempotent module and provide all state-defining arguments. A shell command that always returns success does not automatically tell Ansible that the desired state already exists. For unavoidable commands, design an explicit test or condition that distinguishes the already-correct state.
A handler never runs
Check that the notifying task actually reports changed, that the handler is under the play’s handlers: key, and that its name matches the value in notify. A task that is skipped or reports ok does not trigger the handler.
YAML parses but the task behaves incorrectly
Inspect indentation and data types. Quote modes, paths containing special characters, and string values that could be interpreted as booleans or numbers. Keep module arguments below the module key, and keep task keywords such as loop, when, and register aligned with the module key rather than nesting them inside its arguments.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Check mode gives an incomplete picture
Confirm whether the module supports check and diff behavior in the Ansible version installed on the controller. A clean check run cannot predict an operation that the module cannot simulate, so validate such tasks in a controlled environment.
Choosing a task pattern
| Need | Recommended pattern | Reason |
|---|---|---|
| Set one resource to a desired state | One task using a purpose-built FQCN module | Readable intent and module-managed idempotence |
| Apply the same state to several values | One task with loop |
A single definition avoids duplicated arguments |
| Run only on matching hosts or items | when at task level |
The condition is evaluated where the decision belongs |
| Use output from an earlier operation | register followed by a later expression |
Preserves the earlier result for an explicit dependency |
| Reload or restart after a real configuration change | notify plus a handler |
Follow-up work happens only after a changed result |
| Share a group of tasks | import_tasks or include_tasks |
Separates reusable task files while retaining normal task syntax |
Pre-run checklist
- Each task has a specific
name. - The module is identified with an appropriate FQCN.
- Arguments are indented below the module and values with surprising YAML types are quoted.
- Variables represent environment-specific values and are referenced with Jinja2 expressions.
- Loops use a clear item shape and a deliberate loop variable when necessary.
whenexpressions omit{{ }}and are tested against the intended facts or variables.- Configuration changes notify a correctly named handler when a follow-up service action is required.
- Task order supplies prerequisites before dependents.
--syntax-check, host and task listings, and appropriate check or diff previews have been run.
With these rules, a task remains a small, inspectable declaration: a named action, one module, explicit arguments, and optional controls that explain when and how it should run.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
