Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-8684

mysql : Need exposure of mysql_grant and mysql_user type

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: mysql
    • Labels:
      None
    • Environment:
      • CentOS 7 
      • Puppet 5.5 Open Source
      • MySQL 5.7
    • Template:
    • Team:
      Modules
    • QA Risk Assessment:
      Needs Assessment

      Description

      In the puppetlabs-mysql module, both the mysql_grant and the mysql_user types have been designated as api-private.

      I'm wondering if this designation could potentially be removed due to more advanced use cases.  For example, as of now, using the properly public entities, I could create a database on a server with a single user that connects to the database and has specified rights.  This works in fairly simple cases; but, I'm in an environment where we'd need multiple user definitions.

      To clarify, we have web applications distributed among many machines behind a load balancer.  These applications have a profile defined type built internally to ensure everything necessary about the application is available.  These applications also need access to a database on a central server.  Right now, each individual grant for a user at one of these hosts behind the balancer is a manual configuration change within MySQL.  Using the mysql_grant and mysql_user types, I was able to export a resource from each web server with the appropriate user and grant and collect them on the database server.  This works very well; but, it employs an API that's marked private (and thus subject to change).

      Let me know if I'm missing a nuance about how the public types operate.

      Thanks for the help.

        Attachments

          Activity

            People

            Assignee:
            david.swan David Swan
            Reporter:
            abondmpr Aaron
            Votes:
            5 Vote for this issue
            Watchers:
            8 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support