Cannot get a config item into my.cnf without a value

[tekenny]

It seems that my.cnf forces a value to exist for every option specified in my.cnf
However, there are some options such as no-auto-rehash which must not have a value

[apenney]

I need to look at this more closely as this whole "some keys don't need values" thing caused me nothing but a headache in testing and I discovered that MySQL didn't seem to care if ones that didn't need values had one. Obviously that doesn't apply globally if this issue is right which is a pain.

I had originally built it so that things left blank would automatically create just "key" instead of key = value but I ran into issues there which made me end up just going for values on everything. Let me pull this in locally and do some testing.

[tekenny]

Unfortunately mysql does require some options NOT to have options. I also have a condition where some options that the module defines need to be removed.

I've made an additional change to the template so that specifying false will not put that item in the file. However if you really need option = false you can specify option => 'false'

I'm new to contributing back to the community but let me know how I can be of assistance. Thanks!

[apenney]

Yeah, I think that what we have is the best compromise we can reach. I ran it through the rspec-system tests and those seemed OK so it hasn't caused any regressions I can find. I've merged in the PR.

[tekenny]

My first merged PR on GitHub, thanks!

[apenney]

I am happy to merge lots more if you submit them! :)