Currently there isn't anything provided by Quarkus that allows to persist Quarkus devservices databases. We have needs of developing using a database that is going to have a lot of migrations and potentially lot of data, which may become cumbersome if database container is spin, migrated and populated every time the application starts.
We could simply not use devservices but in any case wouldn't be useful to have a way of using Docker volumes for devservices database?
Implementation ideas
Maybe a way of using volumes could be a property quarkus.datasource.devservices.volume=some_volume that will reuse some_volume existing volume with the spin Docker container.
Description
Currently there isn't anything provided by Quarkus that allows to persist Quarkus devservices databases. We have needs of developing using a database that is going to have a lot of migrations and potentially lot of data, which may become cumbersome if database container is spin, migrated and populated every time the application starts.
We could simply not use devservices but in any case wouldn't be useful to have a way of using Docker volumes for devservices database?
Implementation ideas
Maybe a way of using volumes could be a property
quarkus.datasource.devservices.volume=some_volume
that will reusesome_volume
existing volume with the spin Docker container.