Skip to content

mysql::secure class #3

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

Open
wants to merge 2 commits into
base: feature/master/use_mysql_gem_for_provider
Choose a base branch
from

Conversation

justinellison
Copy link

Here's a small feature addition, one bug fix, and one example of how to trigger a bug I can't figure out :)

MySQL ships with a shell script named mysql_secure_installation. It removes test dbs, anonymous users, etc. Productionize.pp is a port of that into puppet.

There's one bug fix in the type - in the case of an anonymous user, the string before the @ sign is nil.

Note that this branch has a bug, and it's one I can't figure out. Any time I set the ensure property on the database_grant type, I get an error, even though puppet describe says I can set it.

@justintime
Copy link

Please note that there's an error when you apply mysql::secure: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter ensure at /etc/puppet/environments/mysqlgem/modules/mysql/manifests/secure.pp:16 on node mysql.foo.com

I have no idea why I can't set the ensure property, but I'm about 99% sure it's not coming from this commit, rather from the type itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants