Closed falon closed 3 years ago
Thanks for the report, I've applied your suggestion and created a new release. For some reason it was working for me, I guess every time I ran the playbook it was also restarting 389DS in the previous task due to other changes.
Thank you to add this.
I saw at the commit. Did you forget the tags: dirsrv_schema
?
If I run the role for schema reloading only, if the tag is not present then the schema will never reload.
Oops, my bad, I've added the tags now
https://github.com/lvps/389ds-server/blob/8b151c4e23d3789fc27d168f05bcdc34ffcf2300/tasks/main.yml#L102-L119
Maybe you mean
In this way it works very pretty for me.