bundlewrap
MySQL database and user item
@vain I'm retagging this as design-decision. Do we really want to manage MySQL and Postgres databases and users? Doing this reliably across distributions seems like a major PITA. Considering these things usually don't change very often, I doubt it's worth the effort. Thoughts?
This is tricky.
I think of Blockwart as the tool that manages my configuration, not my data. So, when a system crashes, I want to be able to do a "bw apply", have (almost) everything configured and then re-install my data from a backup.
Are MySQL users data or configuration? Configuration, you'd say, just like system users. But: A full MySQL dump includes the users. So they're "data" as well, as they can be easily restored from a dump. (I have no idea about Postgres, though.) Sort of a grey area.
Yes, implementing this is going to be nasty. Would it be nice to have this feature? Oh, yes. Do we need it? Given the amount of unmanaged MySQL databases/users we have right now, I'd say no. What we need is some way to do automated backups of databases -- but we don't need to fully manage the databases to do so.
I'm fine with not implementing this, although my gut tells me it's too important to be left out.
PS.: I have no personal interest in this feature since I don't use any SQL databases whatsoever on my private systems.
I agree. Let's leave this open, but it's not a priority for the next six months or so.