Similar to the WiremockResource, we can provide the DB only on tests need it (or in general) with a QuarkusTestResourceLifecycleManager, which will allow:
Remove from both the dev and test profiles the DB configuration
Remove the DB on the .tmp folder on QuarkusTestResourceLifecycleManager stop
Fine-grained configuration if we need it from different tests
This is marekd as a low priority because although it simplifies the development, it is not a big change as we already have the DB on disk with the current configuration.
Similar to the
WiremockResource, we can provide the DB only on tests need it (or in general) with aQuarkusTestResourceLifecycleManager, which will allow:devandtestprofiles the DB configuration.tmpfolder onQuarkusTestResourceLifecycleManagerstopThis is marekd as a low priority because although it simplifies the development, it is not a big change as we already have the DB on disk with the current configuration.