Release 3.4.0 commit

changelogs/fragments/0-mysql_db_add_chdir_argument.yml

@@ -1,2 +0,0 @@
-minor_changes:
-- mysql_db - add the ``chdir`` argument to avoid failings when a dump file contains relative paths (https://github.com/ansible-collections/community.mysql/issues/395).

changelogs/fragments/1-mysql_replication_can_disable_master_ssl.yml

@@ -1,2 +0,0 @@
-bugfixes:
-- mysql_replication - when the ``primary_ssl`` argument is set to ``no``, the module will turn off SSL (https://github.com/ansible-collections/community.mysql/issues/393).

changelogs/fragments/2-mysql_db_announce.yml

@@ -1,6 +0,0 @@
----
-minor_changes:
-- mysql_db - add the ``pipefail`` argument to avoid broken dumps when ``state`` is ``dump`` and compression is used (https://github.com/ansible-collections/community.mysql/issues/256).
-
-major_changes:
-- mysql_db - the ``pipefail`` argument's default value will be changed to ``true`` in community.mysql 4.0.0. If your target machines do not use ``bash`` as a default interpreter, set ``pipefail`` to ``false`` explicitly. However, we strongly recommend setting up ``bash`` as a default and ``pipefail=true`` as it will protect you from getting broken dumps you don't know about (https://github.com/ansible-collections/community.mysql/issues/407).

changelogs/fragments/fix-256-mysql_dump-errors.yml

@@ -1,7 +0,0 @@
----
-
-bugfixes:
-  - mysql_db - Using compression masks errors messages from
-    mysql_dump. By default the fix is inactive to ensure retro-compatibility
-    with system without bash. To activate the fix, use the module option
-    ``pipefail=true`` (https://github.com/ansible-collections/community.mysql/issues/256).

changelogs/fragments/simplified-bsd-license.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - Include ``simplified_bsd.txt`` license file for various module utils.