The "configure" tag does too much: it deploys configuration files and sets things like user permissions via SQL commands.
The problem with this concept is that "configure" assumes a running MariaDB instance. If MariaDB no longer starts after an update and I want to deploy adjusted configuration files to fix the issue, the role becomes unusable.
Therefore, "configure" should handle configuration files without expecting a running MariaDB instance, and everything else should be moved to a different tag.
The "configure" tag does too much: it deploys configuration files and sets things like user permissions via SQL commands.
The problem with this concept is that "configure" assumes a running MariaDB instance. If MariaDB no longer starts after an update and I want to deploy adjusted configuration files to fix the issue, the role becomes unusable.
Therefore, "configure" should handle configuration files without expecting a running MariaDB instance, and everything else should be moved to a different tag.