Thank you sir. I am not sure why, but it works with or without the status:
line. Todd found what was breaking my playbook, though. I did add the
status: line just to be consistent, and for readability in the future.
I appreciate both of your assistance, and I hope to contribute in the
future.
You specify the what. You don't specify the action. You need a state (ie
present, absent, etc).
- name install standard stuff
apt:
name: {{ applications }}
state: present
Walter
--
Walter Rowe, Division Chief
Infrastructure Services, OISM
Mobile: 202.355.4123
On Aug 1
Wow, thanks for the speedy reply!
Unfortunately for me, that didn't work (adding 2 spaces further indent on
the line " name: {{ applications }} " although it does make sense.
I still get the same error, at the same point. Kinda frustrating when the
keyword "name:" can be used for several dif
Does your 'name' line in your apt task needs to be indented?
- name install standard stuff
apt:
name: {{ applications }}
... should be ...
- name install standard stuff
apt:
name: {{ applications }}
Walter
--
Walter Rowe, Division Chief
Infrastructure Services,
New user of ansible. I've tried several playbooks to use as templates.
My goal is to create a vars.yml with the following:
= = = = =
---
applications:
- app1
- app2
- app3
- and so on
...
= = = = =
and file inventory contains list of new_machines (with appropriate link in
ansible.cfg)
