Open juangon opened 2 years ago
@juangon if you would like to start the devmode in combination with the external docker-compose, you should disable devservices, not only the data index but probably any other that Quarkus would start automatically.
You can either disable only data index by setting quarkus.kogito.devservices.enabled=false
to your application.properties or disable Quarkus devservices completely by adding quarkus.devservices.enabled=false
.
More information about Dev Services is available at https://quarkus.io/guides/dev-services and https://quarkus.io/guides/kogito-dev-services#enabling-disabling-dev-services-for-kogito
Thanks @cristianonicolai but doing that disables /q/dev, which is the thing I want to play with.
So, that doesn't work. Any other alternative?
Strange, that should only disable dev services, not the dev ui afaik. Unless you mean you want to access Data Index via /q/dev?
No no, I just want to access Kogito Forms to play with them in Dev UI
Oh wait @cristianonicolai , it seems is due to the authentication in root path in these demos....
quarkus.http.auth.permission.authenticated.paths=/*
quarkus.http.auth.permission.authenticated.policy=authenticated
Let me check
Ok @cristianonicolai I don't have any runtime kogito tools in dev UI even when adding:
<dependency>
<groupId>org.kie.kogito</groupId>
<artifactId>runtime-tools-quarkus-extension</artifactId>
</dependency>
And no Kogito runtime tools dev/UI:
@pefernan @paulovmr any ideas?
@juangon hi!
just a question, are you starting the docker-compose
in your project? maybe the data-index started there is clashing with the data-index started by kogito in dev mode. If you want to use the dev-ui you may not need the docker-compose started (unless you need the oidc).
Regarding the extension issue here, looks like it's not able to locate the process related features in your project... do you have the process-management addon dep?
<dependency>
<groupId>org.kie.kogito</groupId>
<artifactId>kogito-addons-quarkus-process-management</artifactId>
</dependency>
Hi @pefernan, yes I am testing oidc too so it seems I need docker compose.
And yes, I have that dependency
I am experiencing the same issue with the kogitio-examples stable branch. Was @juangon ever able to resolve this issue?
Describe the bug
I am trying to execute dev services withing process-usertasks-with-security-oidc-quarkus-with-console kogito demo, but it throws an error about same port conflicting for data index. Notice that these demos require startServices.sh script to work, so Data Index already exists and is running.
After reading documentation, I realized data index container name was different in docker-compose comparing to default value (data-index vs kogito-data-index), so I tried setting:
quarkus.kogito.devservices.service-name=data-index
but didn't work.
How can I execute dev services in these demos?
Thanks.
Expected behavior
Dev services are started without any error
Actual behavior
Port conflict error:
How to Reproduce?
Steps to reproduce: 1-Follow instructions on README 2-When starting Quarkus service, do it by
mvn clean quarkus:dev
3-See error thrownOutput of
uname -a
orver
Linux Ubuntu
Output of
java -version
11
GraalVM version (if different from Java)
No response
Kogito version or git rev (or at least Quarkus version if you are using Kogito via Quarkus platform BOM)
stable
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response