Skip to content
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

Refactor MySQL bindings and client packages. #232

Merged
merged 1 commit into from
Jul 23, 2013
Merged

Refactor MySQL bindings and client packages. #232

merged 1 commit into from
Jul 23, 2013

Conversation

apenney
Copy link
Contributor

@apenney apenney commented Jul 19, 2013

The current MySQL module is hard to modify, test, and drop in
replacement components to. This work starts out by refactoring
the bindings support in MySQL to a completely seperate bindings
class in order to reduce the amount of parameters in the main
class for a feature that is infrequently used.

In addition to this start the movement of client configuration
and packages to the mysql::client::* namespace.

The current MySQL module is hard to modify, test, and drop in
replacement components to.  This work starts out by refactoring
the bindings support in MySQL to a completely seperate bindings
class in order to reduce the amount of parameters in the main
class for a feature that is infrequently used.

In addition to this start the movement of client configuration
and packages to the mysql::client::* namespace.
apenney pushed a commit that referenced this pull request Jul 23, 2013
Refactor MySQL bindings and client packages.
@apenney apenney merged commit 1820b05 into puppetlabs:master Jul 23, 2013
@apenney apenney deleted the refactor-round-1 branch July 23, 2013 18:16
$python_package_name = $mysql::params::python_package_name,
$ruby_package_ensure = $mysql::params::ruby_package_ensure,
$ruby_package_name = $mysql::params::ruby_package_name,
$ruby_package_provider = $mysql::params::ruby_package_provider,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This requires puppet 2.7+. Is this change intentional or just an oversight?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wouldn't say it's an intentional change but we're no longer actively supporting 2.6 in any way. It's beyond end of life and we're no longer testing modules against it or ensuring that it stays working. We'll take minor patches like dropping the last comma, but we're.. actively pushing for people to move up. :)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since it's a minor patch, I created #235. We also started the discussion about supporting 2.6 in the foreman installer.

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.

4 participants