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

Issue #41447 - support AWS Aurora S3 privileges in mysql_user module #50454

Open
wants to merge 1 commit into
base: devel
from

Conversation

Projects
None yet
2 participants
@bpennypacker
Copy link
Contributor

bpennypacker commented Jan 2, 2019

SUMMARY

Fixes #41447

Adds 'LOAD FROM S3' and 'SELECT INTO S3' to the list of valid privileges so AWS Aurora accounts can include them.

ISSUE TYPE
  • Bugfix Pull Request
COMPONENT NAME

mysql_user

ADDITIONAL INFORMATION

See the discussion in #41447 for details.

In a nutshell, this PR allows AWS Aurora users to include the above mentioned privileges. This will not break exiting use of the mysql_user module in any way as it only adds to the list of valid privileges that the module checks for. Even if a regular mysql user were to attempt to reference these privileges they would simply receive an error from the mysql server rather than an error from ansible itself.

Example before adding this PR:

TASK [mysql-users : manage mysql role users] **************************************************************************************************************************
failed: [localhost] (item=uat1) => {"changed": false, "item": {"key": "uat1", "value": {"password": "xxxxxx", "priv": "uat1.*:ALL/*.*:LOAD FROM S3,SELECT INTO S3"}}, "msg": "invalid privileges string: Invalid privileges specified: frozenset(['LOAD FROM S3', 'SELECT INTO S3'])"}

After:

TASK [mysql-users : manage mysql role users] **************************************************************************************************************************
changed: [localhost] => (item=uat1)
@ansibot

This comment has been minimized.

Copy link
Contributor

ansibot commented Jan 2, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment