Allow changing the mysql-config-file group-ownership

[unki]

With my PR #1278 it's now possible to change the file-permission-mode of the mysql-config-file - e.g. my.cnf.

If you are trying now to apply a rather strict file-mode like 0600 - in combination with Puppet's default file-ownership root:root - it will lead to issues with MariaDB not being able to access the config-file after it has switched the processes to the service-user (e.g. mysql).

Therefor I would propose additionally using $mysql::server::mysql_group as the mysql-config-file's group-ownership. Then restricting access would be easy done with a 0640 file-mode.

[codecov-io]

Codecov Report

❗ No coverage uploaded for pull request base (master@8b2591f). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1284   +/-   ##
=========================================
  Coverage          ?   14.53%           
=========================================
  Files             ?       19           
  Lines             ?      860           
  Branches          ?        0           
=========================================
  Hits              ?      125           
  Misses            ?      735           
  Partials          ?        0

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8b2591f...97ef2ca. Read the comment docs.

[michaeltlombardi]

Hey @unki, thanks for this patch! Can you rebase your PR on latest master and repush? I believe that may fix your CI issue.

[TwizzyDizzy]

Hey @unki,

thanks also for this... seems like we had the same thoughts. What I don't get, is why you - in your second commit - decided not to use $mysql::server::root_group but introduce those new variables for mycnf-ownership. Did using $mysql::server::root_group have side effects that made those new variables necessary?

Cheers & thanks in advance :)
Thomas