Closed jbradberry closed 7 years ago
Here and elsewhere, I'm wondering when we have more than a couple tasks in a row that only run when the same condition is true, if it'd be clearer if we moved those tasks to another file and used a conditional include instead of having them all in main?
Hm, intriguing. Yes, I think I might like that. (The conditional includes, that is.)
Or we could use the new block
feature in Ansible 2.0 if we're willing to require Ansible 2.0. (Which wouldn't bother me at all.)
I went with the conditional include, for now.
We need to do an "apt-get update" before trying to install any packages.
Can we add something like this as the first task, to prevent a bad configuration from locking everyone out of the deployed systems?
- name: make sure we've defined some dev users
fail: msg="Please define one or more developers in the `users` variable"
when: users|length == 0
@poirier r? I believe I've addressed all of your review comments.
:shipit: I haven't tried it, but I assume you have and it looks reasonable.
P.S. at work I'm @dpoirier. The poirier ID is my personal account.
Merging together the old
common
andstructure
roles, and splitting off into its own repo, to support installation usingansible-galaxy
.