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

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

Closed
wants to merge 1 commit into from
Closed

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

wants to merge 1 commit into from

Conversation

bpennypacker
Copy link
Contributor

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
Copy link
Contributor

ansibot commented Jan 2, 2019

@ansibot ansibot added affects_2.8 This issue/PR affects Ansible v2.8 bug This issue/PR relates to a bug. community_review In order to be merged, this PR must follow the community review workflow. module This issue/PR relates to a module. needs_triage Needs a first human triage before being processed. small_patch support:community This issue/PR relates to code supported by the Ansible community. labels Jan 2, 2019
@ansibot ansibot added the stale_ci This PR has been tested by CI more than one week ago. Close and re-open this PR to get it retested. label Jan 10, 2019
@ansibot ansibot added the needs_repo This PR no longer has an associated branch as it was removed by the submitter. label Jan 18, 2019
@ansibot ansibot removed the needs_triage Needs a first human triage before being processed. label Jan 28, 2019
@gundalow
Copy link
Contributor

@bpennypacker Hi, When I merged https://github.com/ansible/ansible/pull/51478/files that caused a merge conflict in your PR. Would you be able to rebase then we can get this feature merged?

@gundalow
Copy link
Contributor

We have a MySQL Working Group that's working through the backlog of MySQL PRs.

@ansibot
Copy link
Contributor

ansibot commented Feb 19, 2019

@ansibot ansibot added database Database category needs_rebase https://docs.ansible.com/ansible/devel/dev_guide/developing_rebasing.html needs_revision This PR fails CI tests or a maintainer has requested a review/revision of the PR. and removed community_review In order to be merged, this PR must follow the community review workflow. labels Feb 19, 2019
@ansibot
Copy link
Contributor

ansibot commented Feb 27, 2019

@ansibot
Copy link
Contributor

ansibot commented Jun 4, 2019

@ansibot
Copy link
Contributor

ansibot commented Jun 20, 2019

@ansibot
Copy link
Contributor

ansibot commented Jul 31, 2019

@bpennypacker Your branch does not contain a shippable.yml file. Please rebase your branch to trigger running of current tests.

click here for bot help

@ansibot ansibot added the needs_shippable This PR lacks a shippable.yml in its tree. Please rebase your branch to include the latest CI tests. label Jul 31, 2019
@ansibot
Copy link
Contributor

ansibot commented Jul 31, 2019

@bpennypacker Your branch does not contain a shippable.yml file. Please rebase your branch to trigger running of current tests.

click here for bot help

@ansibot
Copy link
Contributor

ansibot commented Aug 8, 2019

@gundalow
Copy link
Contributor

gundalow commented Sep 3, 2019

Has been replaced by #59663 please review that so we can get it merged.

@gundalow gundalow closed this Sep 3, 2019
@gundalow gundalow added the pr_day Has been reviewed during a PR review Day label Sep 3, 2019
@ansible ansible locked and limited conversation to collaborators Oct 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.8 This issue/PR affects Ansible v2.8 bug This issue/PR relates to a bug. database Database category module This issue/PR relates to a module. mysql needs_rebase https://docs.ansible.com/ansible/devel/dev_guide/developing_rebasing.html needs_repo This PR no longer has an associated branch as it was removed by the submitter. needs_revision This PR fails CI tests or a maintainer has requested a review/revision of the PR. needs_shippable This PR lacks a shippable.yml in its tree. Please rebase your branch to include the latest CI tests. pr_day Has been reviewed during a PR review Day small_patch stale_ci This PR has been tested by CI more than one week ago. Close and re-open this PR to get it retested. support:community This issue/PR relates to code supported by the Ansible community.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

No way to grant SELECT INTO S3 for AWS Aurora user
5 participants