On 27/01/2015 19:49, Alec Ten Harmsel wrote: > > On 01/27/2015 11:33 AM, Alan McKinnon wrote: >> On 27/01/2015 10:49, Tomas Mozes wrote: >>> I haven't tested it yet, however I like the minimalistic syntax. >>> >>> As an ansible user - do you plan to allow using default values for >>> modules and/or variables? >> >> +1 for that. >> >> I'm also a happy ansible user with zero plans to change, but I can't >> imagine a deployment tool without sane rational explicit defaults. A >> whole host of problems simply stop being problems if that feature is >> available. >> > > I'm curious, what exactly do you mean about default values? Is there a > small example you can give me? The tutorial on Ansible's website is a > little confusing.
When I saw your other reply to Tomas, I thought you might ask that question :-) What I was thinking of is defaults like you find in roles on galaxy. In a sub-dir called defaults you find a file main.yml containing variables defaults as key-value pairs. A good example is Stouts.openvpn, it has eg openvpn_port: 1194 openvpn_proto: udp If you don't define those vars yourself in the playbook, the role uses those defaults, which is exactly what you want - they match upstream default. The location is very explicit, the defaults are in a named file in an obvious location and there's no mysterious automagic. I definitely wasn't talking about crazy magic permission modes like the suggestion you mentioned in the other mail. A default mode is fine, but make it a variable called "mode" or "umask" that we can see in a file and make it what we want. I think we do agree on this :-) -- Alan McKinnon alan.mckin...@gmail.com
