Mariadb__*_users & mariadb__*_databases custom vars
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 1.4k
- Forks
- 379
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 8
Description
Hello,
I've a question about your "mariadb" role in debops.
I have multiple mariadb host in different mariadb group and i need to create user specific to host and other users specifics to groups.
Example of my inventory :
[Mariadb1]
VM1-mariadb1-test
VM2-mariadb1-example
[Mariadb2]
VM1-mariadb1-test
VM3-mariadb2-testing
Is-it possible for Mariadb1 group to create an user for VM1-mariadb1-test and VM2-mariadb1-example but they also have their own users ?
I saw in the "monit" and some other roles that the task use a "combined" variable containing customs variables and that we have the possibility to add variables thanks to "host_vars" and "group_vars" directory.
Is-it possible to add custom variables like for exemple "mariadb__grouptest_user" without to touch task file but only variables files ? I'm not an ansible expert but like i said, i know it is possible for "monit" role but i don't know for mariadb because it is builded differently : monit use a "with_items" while mariadb use a "loop".
Thanks for your help and to contribute to Debops :)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the mariadb role's task and variable definitions, then compare them with the monit role's combined-variable handling. Check how host_vars and group_vars are consumed for MariaDB users and databases. Done means the requested host- and group-specific custom variables work without task-file edits, with the behavior documented or covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, mariadb
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100