chore(deps): update dependency community.mysql to v3.3.0 #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.2.1
->3.3.0
Release Notes
ansible-collections/community.mysql
v3.3.0
Compare Source
======
Release Summary
This is the minor release of the
community.mysql
collection.This changelog contains all changes to the modules in this collection
that have been added after the release of
community.mysql
3.2.1.Minor Changes
members_must_exist
(boolean, default true). The assertion that the users supplied in themembers
argument exist is only executed when the new argumentmembers_must_exist
istrue
, to allow opt-out (mysql_role: add argument "members_must_exist" ansible-collections/community.mysql#369).on_new_username
to argumentupdate_password
to reuse the password (plugin and authentication_string) when creating a new user if some user with the same name already exists. If the existing user with the same name have varying passwords, the password from the arguments is used like withupdate_password: always
(mysql_user: add "update_password: on_new_username" argument, "password_changed" result field ansible-collections/community.mysql#365).password_changed
(boolean). It is true, when the user got a new password. When the user was created withupdate_password: on_new_username
and an existing password was reused,password_changed
is false (mysql_user: add "update_password: on_new_username" argument, "password_changed" result field ansible-collections/community.mysql#365).Bugfixes
IF EXISTS/IF NOT EXISTS
clause is used (mysql_query returns changed: true when nothing is executed. ansible-collections/community.mysql#268).detach_members: true
is set (mysql_role: don't add members to a role when creating the role and "detach_members: true" is set ansible-collections/community.mysql#367).update_password
is set toon_create
for users usingplugin*
arguments (mysql.user tries to set password on second run with update_password = "on_create" ansible-collections/community.mysql#334). Theon_create
setspassword
to None for old mysql_native_authentication but not for authentiation methods which uses theplugin*
arguments. This PR changes this soon_create
also exchangeplugin
,plugin_hash_string
,plugin_auth_string
to None in the list of arguments to changeConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.