better behaviour when changing passwords & SELinux tune up - under CentOS 8 about ansible-nextcloud HOT 1 CLOSED

Hi Spookie

Thanks for your inputs!

Regarding the mysql root password, we set force: no on some of the templates because we often change these files manually for some of our instances and we want to make sure that these changes do not get lost. But I see your point regarding the root password. For the latest version of rbicker.nextcloud I have added a new task using the lineinfile ansible module to make sure that the mysql root password is correct. So this should solve the random password use case.

Regarding improving selinux. Would you mind opening a new issue for that, so we have one problem / improvement per issue? Some more things:

• Please describe your improvement or the problem you wish to solve.
• If you wan't to provide us with code to run, please do so by using a pull request.
• Your code would need to check if selinux is installed (please have a look at the permissions.yml task file for examples) to make sure it does not break the role for users not using selinux.
• Your code uses namespaces which is not supported in older versions of ansible. Basically this is something that we could use but you would also need to adjust the meta/main.yml accordingly.

Thanks

from ansible-nextcloud.