-
Notifications
You must be signed in to change notification settings - Fork 363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce standardized mapping files #186
Conversation
3d0c389
to
841a4fd
Compare
Rebased with #184 |
ed785ad
to
c55d4f0
Compare
c55d4f0
to
1e826ea
Compare
@noelmcloughlin is this ready for merging? |
Yes, definitely @aboe76 I tested on range of Distros and looks okay. |
@noelmcloughlin thanks for this refactoring |
!includedir /etc/mysql/conf.d/ | ||
# {% if salt['grains.get']('osmajorrelease')|int >= 9 -%} | ||
# !includedir /etc/mysql/mariadb.conf.d/ | ||
# {%- endif %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @noelmcloughlin, today I stumbled with these commented lines in a Debian server. Any reason why you left them disabled?
I can re-add them in an osfingermap.yaml
, I can send a PR if that makes sense. Only wanted to know your reasons before writing anything 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @javierbertoli .. hmm, no harm would arise from uncommenting these I think. @BABILEN introduced these commented lines in #181. My PR was concerned with file refactoring so this got migrated as is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They are commented as the formula manages all settings in /etc/mysql/my.cnf
while some settings that ship in /etc/mysql/mariadb.conf.d/*.cnf
might conflict and override the ones explicitly managed.
If it is being enabled we should make sure, that no settings are shadowed and that all MariaDB settings are handled correctly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@BABILEN yes, I found it the 'hard way': run the formula with that line uncommented dev VM and many of the saw that /etc/mysql/mariadb.conf.d/*.cnf
values overrode the parameters set by the formula.
I suppose the 'correct thing to do' is to manage the parameters in those files instead of cramming them all in the /etc/mysql/my.cnf
file, but that'd mean some heavy refactor atm.
I guess that a good 'simple PR' would be to add a few lines explaining all you mention in the README.md
file, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the end we probably want to have a single source of configuration for this formula, but this is at odds with the .d
approach for MySQL/MariaDB specific configuration in Debian at the moment. I personally like using configuration files in .d
directories, but, as you rightly note, this would require heavy refactoring of this formula.
Apart from documenting it in README.md
, a comment next to the includedir
statement could be added as well.
This PR splits formula data into
defaults.yaml
,osfamilymap
, andosmap
artifacts. This should allow more easier layering, filtering, merging, and distribution via the standardizedmap.jinja
, and will make formula more extensible (i.e. support for MacOS, Workbench, etc).Due to ID collisions between
mysql.server
&mysql.dev
(packages) andmysql:lookup:server
&mysql:lookup:dev
(optional pillar dicts??), I renamed four pkg variables.Resolves #165. Supports #18 and #88; Ignores #80 (confusing issue).
Tested on Ubuntu, Centos, Fedora.
UBUNTU 16 (no pillars)
FEDORA 27 (no pillars)
CENTOS 7 (no pillars)