mysql_* modules defaults from my.cnf
25 views
Skip to first unread message
Michael Peters
Jul 17, 2014, 3:19:01 PM7/17/14
to ansible...@googlegroups.com
Right now the various mysql_* modules will pull default connection
information from the ~/.my.cnf file. This is especially important to
make things repeatable especially when the server is newly provisioned
and insecure.
But it doesn't use the socket information in the ~/.my.cnf file.
Instead if your sever has the socket in a different spot you need to
explicitly set it in every task. Not a huge deal, just slightly
annoying when you don't need to specify the user/pw for each task.
Would a PR be accepted that would use the socket from .my.cnf as the
login_unix_socket if one exists?
information from the ~/.my.cnf file. This is especially important to
make things repeatable especially when the server is newly provisioned
and insecure.
But it doesn't use the socket information in the ~/.my.cnf file.
Instead if your sever has the socket in a different spot you need to
explicitly set it in every task. Not a huge deal, just slightly
annoying when you don't need to specify the user/pw for each task.
Would a PR be accepted that would use the socket from .my.cnf as the
login_unix_socket if one exists?
Michael DeHaan
Jul 17, 2014, 9:39:36 PM7/17/14
to ansible...@googlegroups.com
Sounds great, send us a PR!
--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAJQqANd60222pmKGBNqUm9hi2jv4NAUxs-4d1ugfiBFtw5tJpQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages