Even if a role ends up being a no-op, it takes time. This makes playbook execution slower, which is annoying.
On Wednesday, July 16, 2014 5:22:34 PM UTC-7, Michael DeHaan wrote: > > Generally people should write roles so that they are idempotent (grr, that > word again) and running them more than one time is a no-op. > > If the operation is very destructive and you don't want to run it again, > maybe consider a touch file to indicate the configuration has been done > once. > > I do understand what you mean about not being a dependency anywhere, but > because ansible allows parameterized roles as dependencies, this would also > remove some other use cases if we applied it globally. > > Some roles might allow deps, others might not, etc. The role gets to pick. > -- 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/9acf3a24-0447-4a49-a237-f9af4fab50a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
