This would be done automagically once once the YAML migration is done - the releng's aim is to have configuration stored statically in YAML files, which would mean you would only need a YAML parser to do what you want. Not sure about the migration plan, @Jdforrester-WMF would know that.

Yeah, right now every dblist you add slows down production, so there's a general ban on adding them unless they're crucial for run-time use (and we're trying to drop a bunch of old ones).

I don't know where the project is at, I'm afraid; I think that's now something @jeena is working on.

I don't know where the project is at, I'm afraid; I think that's now something @jeena is working on.

I think this refers to T223602: Define variant Wikimedia production config in compiled, static files which is currently stalled and we've decided to move it to future quarters work as it doesn't necessarily block the migration of m7i -> k8s. Is that a blocker for this task specifically?

An easy way to get such list would make my life easier. It doesn't necessarily need to be implemented as a dblist.