managing users and grants with recent puppetlabs-mysql

[Tim Mooney]

All-

I'm using the open source Puppet 5.x platform, with puppetserver 5.3.6
and puppet-agent 5.5.8 on mostly RHEL 6 and 7 (and soon 8, I suppose).

We're long-time users of puppetlabs-mysql, right now we're on the current
latest (7.0.0).

When we started with puppetlabs-mysql, we wrote our database management
puppet classes to use puppetlabs-mysql's mysql_database, mysql_user and
mysql_grant resources directly. Most of our code still does this.

Recent versions of puppetlabs-mysql have marked those resources as
@api private, though.

There is now a mysql::db define that is part of the public API and
kind of combines all three, but AFAICT it only allows managing one user
for the defined database. Additional users or complicated grants seem
to be beyond that define.

I guess I'm confused about what the new recommended way is to manage users
and grants with puppetlabs-mysql?

I've searched these forums and the web, and other than an outdated and
now incorrect hit on StackOverflow, I'm not finding information on what
should replace *public* use of mysql_user and mysql_grant.

Thanks,

Tim
--
Tim Mooney Tim.M...@ndsu.edu
Enterprise Computing & Infrastructure 701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

[david...@puppet.com]

Tim Mooney

Despite it being labelled as private you should still be able to add additional user's in the same way, creating an additional mysql::grant for each assignment. Sorry I don't have more information.

David

[Tim Mooney]

In regard to: [Puppet Users] Re: managing users and grants with recent...:

> Despite it being labelled as private you should still be able to add
> additional user's in the same way, creating an additional mysql::grant for
> each assignment. Sorry I don't have more information.

Thanks David. We haven't yet made any changes to our code that has been
using mysql_database, mysql_user, and mysql_grant. Those all continue to
work, so you're correct that we can still use them.

We'll keep using them until suitable replacements appear, but that's more
or less what I was trying to discover: what are the replacements for these
resources that have transitioned to "private"? It just seems strange to
me to mark something as private without first having an established
replacement.