On Fri, Jul 18, 2014 at 2:40 PM, Michael DeHaan <[email protected]> wrote:
There are cases (again, parameterized roles) - different roles can have the > same dependency with different parameters, where that doesn't make sense.) > AFAIU, this is exactly the use case for allow_duplicates=yes, isn’t it? It would allow the role to be executed multiple times to accommodate the different parameters. What doesn’t make sense here? On the other hand, currently, setting allow_duplicates=no does not help parameterized roles, nor does it help the *execute at most once* use case. It allows multiple executions if the role is listed explicitly and is also a dependency. it sounds like some people may like a role metadata parameter that is > different from this, that is not allow_duplicates, that is something like > once_per_play or something. > What I’m after is not once_per_play, it’s absolutely once, no matter how many times the role is listed in top-level or included plays, and no matter how many times it’s pulled in as a dependency. If we forget about dependencies for a bit, and consider the case where a role is listed in two plays, which are both included in a top-level role. Should that role be executed multiple times even when allow_duplicates=no? -- 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/CAM19uTBzy2Lfi21v%2BCmP%2BLa6mECYewwFP%2BV1%3DMgmtP-feBvS%3Dw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
