On Friday, August 29, 2014 12:47:07 PM UTC+1, Michael DeHaan wrote: > > I haven't seen the need for this pattern arise much, and my comments on > this still hold. > I've found yesterday that ansible gives the flexibility to add plugins outside its codebase. This is great as I (or anybody else) can keep on experimenting with import_defaults without bothering the main codebase.
I've uploaded include_defaults to a gist: <https://gist.github.com/dvarrazzo/7418a89b7278ff69267c>. Info about how to use it are there too. It still takes a file name as input but I think it would be better if it allowed 'role=NAME' too as option to get the role's default file; I haven't dug enough into ansible internals yet to find how to deal with the roles path resolution (of course if someone knows better patches are welcome). If anybody has found the same limitations I found and wants to give it a go it would be nice to know his comments. This may end up showing the emergence of a use case, in which case ansible developers will make their own choices, or not showing anything at all :) In the meantime it's nice to see the solution can live in just a few people's playbook directories and doesn't need hacking into ansible code. Thank you everybody, have a nice weekend. -- Daniele -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/a2524612-28da-48fb-9c44-a2d840729e05%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
