Pavel Valena

Actually, I think we have the manually enumerated variants solved via inheritance quite well, and I would rather avoid introducing another syntax. To take the earlier example: ```yaml prepare: [...

Yes, I believe this is the case. Why not support it, if the backend supports it? VMs, containers....

Please note that I want to pause the work, reboot my machine and then continue, or just conserve my resources, while debugging 4 (sub)plans, i.e. not running 4 VMs overnight...

> What would the scenario look like? > > ``` > tmt run --id complex-job --until execute > tmt run --id complex-job execute --again > ... > tmt run --id...

I've initally thought that it'd be better to tackle this on the dracut module basis - with `--force-add` to override the list `omit_dracutmodules`. But that doesn't work (as discussed in...

> @pvalena, The original reason for this patch was that we wanted to be able to specify extra confdir via cmdline, and it was not intended to overwrite existing confdirs(/etc/dracut.conf.d...

> Honestly, I don't have a strong opinion about this. The use case makes sense, and I think any of these solutions would be safe to backport to downstreams. But...

> When "dracutmodules" or "omit_dracutmodules" are set by bootc conf, some modules such like nfs will not be included into initrd. I think there should be another issue. I think...

Oh, looking at it again, I can now see you want to `omit_dracutmodules` cleared. Dracut currently does not support that (hence the `--force-add` usecase), but I prefer the profiles proposal...

Tested: https://gist.github.com/pvalena/f8cdb9aab623e2f713d823df1824fa72 Should I change/clarify `--help` or man pages; e.g. the `--force-add` option or the `dracut.conf` docs?