Quarkus Dev Services credential reuse for integration tests

Goal: enable integration tests to use a consistent, non‑production credential set while still letting Quarkus Dev Services manage the lifecycle of a temporary database container.

Constraint: Dev Services always generates a new random username and password for each test run and does not expose a way to inject pre‑defined credentials or bind to an external secret store. Uncertainty: whether a configuration exists to override the generated credentials or to have Dev Services read them from an external source without disabling automatic container start/stop.

• Is there a property to supply a static username/password that Dev Services will use instead of generating random values?
• Can Dev Services be configured to obtain credentials from an external secret store (e.g., Kubernetes Secrets, HashiCorp Vault) while still managing the container lifecycle?
• If neither is possible, what is the recommended pattern to achieve reusable non‑production credentials without disabling Dev Services?