ansible-collections/community.mysql
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.mysql.git synced 2025-08-06 22:24:24 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Revert "sync fork with upstream main"

Browse source 
This reverts commit 77593b7a91e8d417eead0d3d5366ba991c767565.
I imported PR569 to be able to test on my fork, but to avoid polluting
this patch I now revert those commit.
This commit is contained in:
Laurent Indermuehle 2023-10-10 11:01:59 +02:00
commit 5477603583
No known key found for this signature in database
GPG key ID: 93FA944C9F34DD09
17 changed files with 56 additions and 437 deletions
Download patch file Download diff file Expand all files Collapse all files

21
changelogs/569_fix_column_uppercasing.yml
View file

@ -1,21 +0,0 @@
---
minor_changes:
- mysql_user - add ``column_case_sensitive`` option to prevent field names
from being uppercased
(https://github.com/ansible-collections/community.mysql/pull/569).
- mysql_role - add ``column_case_sensitive`` option to prevent field names
from being uppercased
(https://github.com/ansible-collections/community.mysql/pull/569).
major_changes:
- mysql_user - the ``column_case_sensitive`` argument's default value will be
changed to ``true`` in community.mysql 4.0.0. If your playbook expected the
column to be automatically uppercased for your users privileges, you should
set this to false explicitly
(https://github.com/ansible-collections/community.mysql/issues/577).
- mysql_role - the ``column_case_sensitive`` argument's default value will be
changed to ``true`` in community.mysql 4.0.0. If your playbook expected the
column to be automatically uppercased for your roles privileges, you should
set this to false explicitly
(https://github.com/ansible-collections/community.mysql/issues/578).

11
changelogs/fragments/drop_ansible_core_2_12_and_2_13.yml
View file

@ -1,11 +0,0 @@
---
major_changes:
- The community.mysql collection no longer supports ``ansible-core 2.12`` and
``ansible-core 2.13``. While we take no active measures to prevent usage
and there are no plans to introduce incompatible code to the modules, we
will stop testing those versions. Both are or will soon be End of Life and
if you are still using them, you should consider upgrading to the
``latest Ansible / ansible-core 2.15 or later`` as soon as possible
(https://github.com/ansible-collections/community.mysql/pull/574).