On Friday, December 20, 2013 at 7:07 AM, Yves Dorfsman wrote:
> On 2013-12-06 17:32, Matt Cordial wrote: > > Say I want to put basic config variables in roles/*/vars/main.yml for use > > when > > the role's tasks run, but also want to access them in a play that doesn't > > include that role. A specific example of what I am talking about would be > > where I need to build a configuration file for an application that is > > configured in a subsequent play. > > > > > Another way of doing this is to use the dictionary ability of yaml, instead > of > adding them in the role, add them to group_vars/all.yaml in a dictornary: > > mysoftware: > license_key: 12345 > version: 2.0 > > Yes, but this doesn’t seem ideal. Especially with the release of galaxy. IMO if we are using galaxy as a means to share code. The roles we share should include vars that can (defaults/main.yml) and cannot (vars/main.yml) be overridden. IMO, if the memcached role defines a port or path, that port should be available to the entire system. > -- > Yves. > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > (mailto:[email protected]). > To post to this group, send email to [email protected] > (mailto:[email protected]). > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
