I see, in that case, notify when you install ldap (only if you use state=present, not state=latest, that would wipe db`s at every openldap upgrade).
yum: name=openldap state=present notify: remove_test_db Or use stat module in the "check for example db", it should not failed status that you get with grep. 2013/12/16 Marc Patermann <[email protected]> > David, > > David Karban schrieb (16.12.2013 17:47 Uhr): > > how many files are there? You are writing "This files have to be >> removed", but you are testing only one file. >> > The problem is, that most of the files will have the same name in the > "production" database. The DB_CONFIG.example is (the) one file which will > not the used later. And thats why it is a good indicator for an existing > example database. > > > If it is only several files, maybe just delete them by file module >> like this: - name: Ensure example db do not exists file: name={{ >> '/var/lib/ldap/' + item }} state=absent with_items: - >> DB_CONFIG.example - DB_CONFIG.example1 >> > That is not possible. See above. I would delete production files later. > > > Marc > > -- > 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. > -- David Karban Specialista na správu linuxových serverů www.karban.eu -- 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.
