Closed hguerrero closed 1 year ago
/cc @stuartwdouglas
@hguerrero is the other image really compatible? (very same command to start and file structure)
@hguerrero Ping.
@cescoffier what is the current command?
Yes, I can confirm those values work.
I just noticed that the console is not exposed (based on the code you share) besides that, it should work.
Do we need to expose the console?
BTW do you have the coordinate of the image you want to use?
Any update on this? I'd like to use the downstream image with customers, i.e.:
quarkus.amqp.devservices.image-name=registry.redhat.io/amq7/amq-broker-rhel8:7.11.0
gahealy@rh
@garethahealy Sorry, I missed your update. I'm going to add this issue to the roadmap.
Description
Currently, only the artemiscloud images are available to deploy the amqp broker container image. However, other compatible images like Red Hat AMQ Broker (based on ActiveMQ Artemis) can be used for dev purposes. But, there if you set this image name, you get an error that is not supported.
Implementation ideas
If I understand correctly, the container images valid for dev services are hardcoded into the AMQP service, it can be externalized or the RH images can be added to that list.