Skip to content

Remove redundant hard coded replication parameters #224

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

Merged
merged 1 commit into from
Jul 15, 2013
Merged

Remove redundant hard coded replication parameters #224

merged 1 commit into from
Jul 15, 2013

Conversation

3flex
Copy link
Contributor

@3flex 3flex commented Jul 15, 2013

The following new mysql class replication parameters were added in 0.8.0, however the existing hard coded parameters were not removed from the my.conf.erb template:

  • expire_logs_days
  • max_binlog_size

Sorry about the noise with the previous pull request, I saw it failed the tests because I moved the parameters. I didn't see any test for these lines which would be removed so this should be OK. This is my first ever pull request so I was always bound to make a mistake!

The following new `mysql` class replication parameters were added in 0.8.0, however the existing hard coded parameters were not removed from the my.conf.erb template:

- `expire_logs_days`
- `max_binlog_size`
@apenney
Copy link
Contributor

apenney commented Jul 15, 2013

I can't believe we never noticed this. I need to take a day or two and sit down and tear into the specs here. We should probably test each parameter somewhere so this kind of thing doesn't happen again. Thanks for catching this.

apenney pushed a commit that referenced this pull request Jul 15, 2013
Remove redundant hard coded replication parameters
@apenney apenney merged commit 5431d78 into puppetlabs:master Jul 15, 2013
@3flex 3flex deleted the remove-redundant-parameter branch July 15, 2013 21:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants