On 01/27/2015 03:49 AM, Tomas Mozes wrote:
>
> I haven't tested it yet, however I like the minimalistic syntax.
Thanks. Testing is kind of a high barrier; it took me hours to write a
role for jenkins.
>
> As an ansible user - do you plan to allow using default values for
> modules and/or variables?
>
I am not really a fan of default values; I prefer explicitness over
forcing someone to have a complete knowledge of bossman. For example,
one of my coworkers pointed out to me that
file /etc/ssh/sshd_config
should install `/etc/ssh/sshd_config` with whatever owner/permissions it
has on disk in the configuration files directory. In other words, he
wanted the implicit defaults to make it easier. Personally, I think this
is harder because now I have to care about permissions of a file that is
being copied and writing a role; instead I like having explicit roles in
which it is mandatory to type
file /etc/ssh/sshd_config root:root 600
This makes it easier to see everything on the same terminal, don't have
to care about local permissions, etc. I'm trying to write a config
manager that has the fewest amount of "gotchas" possible, and I think
that means that a role should explicitly describe the state a machine
should end up in.
I do not have variables, but I might add them if someone gives me a
compelling use case that cannot be done without them.
If this didn't answer your question, my bad. Thanks for the feedback. I
know a lot of the people on this list work full-time and have families;
there's always time to procrastinate on homework though ;)
Alec
