Consul as a Dev Container in DevServices

[krickert]

There are a lot of things in consul that are useful -

I found a way to get the dev services to start with consul and share the consul instance with multiple launches. The thing is, I'm pretty sure the only way to make it work is to hack the hell out of it.

Instead of using CDI, we were able to get it working by using the new java service loading mechanism and forcing a static initializer - this solved the problem of starting consul. On top of that, had to look in the docker instance to see if it was already running... after both of those were set, we were able to get consul CDI to properly start up with consul config turned on.

So what I'm wondering - is there an easier way to do this? Since consul config loads the config, I can get why this is officially a chicken and egg problem... I'm surprised though that I had to do this much effort -

Which leads me to say - maybe with dev services we can define "bootstrap" services - these would run it's own CDI loader that is separate.. I'm new to quarkus, so I'm curious if this has already been done?

[cescoffier]

Could you tell me if you are trying to share a Consul instance between multiple Quarkus apps running in dev mode? Or do you want to keep the dev service running between multiple "run"?

Currently, we have a working group (Dev Service Lifecycle) trying to address these cases. I know they will be interested in your use case. You can reach them directly from Zulip (#dev > WG #49 Dev Service Lifecycle chat)

\CC @holly-cummins @ozangunalp