I use a dedicated Maven profile to include dependencies needed for runtime application inspection (actuators, observability). I.e. ones, I usually don't need during development but only occasionally. If I set up observability libraries to e.g. consume Zipkin, I'd like to have a Zipkin server running. Adding a docker-compose.yml file, however, will cause the server started unconditionally, not only if the profile is enabled.
It would be nice if "profiled" Docker compose config files (docker-compose{-profile}.yml) could be considered by default. Alternatively, fixing GH-25 would allow me to avoid the explicit Docker compose file entirely.
I use a dedicated Maven profile to include dependencies needed for runtime application inspection (actuators, observability). I.e. ones, I usually don't need during development but only occasionally. If I set up observability libraries to e.g. consume Zipkin, I'd like to have a Zipkin server running. Adding a
docker-compose.ymlfile, however, will cause the server started unconditionally, not only if the profile is enabled.It would be nice if "profiled" Docker compose config files (
docker-compose{-profile}.yml) could be considered by default. Alternatively, fixing GH-25 would allow me to avoid the explicit Docker compose file entirely.