-
Notifications
You must be signed in to change notification settings - Fork 24
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
Adds support for Rocky Linux #40
base: main
Are you sure you want to change the base?
Conversation
Hi @digiserg! Thanks for the PR. Can you please explain shortly why you think this PR is needed and what it brings to the role? |
- Support for setting the root user password - It is possible to install additional packages required by MariaDB - Configure MariaDB using `mariadb_options` - Fixes users creation for servers requiring authentication - Adds support for SSL
Hi @fauust You've done a very good job with this role but after I started using I found a few things I require. I understand these are quite a lot of changes and I'll maintain my own fork if you're not happy with them but I thought I should contribute.
Thank you for the great work. |
The more people use and contribute to this role, the better it will become. So, if we can make it work for your needs, let's do it!
This surprises me, first because the role testing should fail in the CI, then because I have just tested and ❯ podman run -it rockylinux:9 bash -c "dnf install ansible-core -y && ansible -m setup localhost | grep ansible_os_family"
[...]
"ansible_os_family": "RedHat",
I am not against adding this feature to the role, but just for curiosity, and since the default root authentication method is unix socket (since MariaDB 10.4), why do you need it in your deployments? In any case, I would like that any new feature comes with the corresponding testing if possible.
What prevents you to use the mariadb_package:
- mariadb-server
- mariadb-pam Adding a new var for extra package could be cleaner though.
When possible, I am strongly against using dictionaries for variables in ansible, in my experience using raw variables is much easier and maintainable. But if you have good reason doing so, I could consider it.
Same comment as before, you could (and probably should) use unix socket here but you may have a very good reason not to.
That could be a great feature to add, I am not sure how we could test this in the CI but I can probably help you. In any case and as said, I prefer that we use raw variable. Here I am not against adding a specific SSL block with a var like
🙏 |
Interestingly, my Rocky instances are in AWS using the AWS Marketplace:
I'm deploying to secure environments such as banking. |
If possible, can you give more information on the setup so I could test?
Can you develop? root authentication via password does not bring any extra security, it's the contrary actually. See also https://mariadb.org/authentication-in-mariadb-10-4/ |
The lack of a password doesn't mean its an empty password. So a password set is another exploit avenue. https://mariadb.com/kb/en/authentication-plugin-unix-socket/#security |
No description provided.