Closed jfriedenstab closed 1 month ago
@wollefitz I think we should only merge this PR after the 8.6.0
release when the cluster configuration feature is available.
@wollefitz Yes, what I actually meant was to merge the PR as part of the 8.6.0 release (assuming that the feature will be ready in Web Modeler 8.6.0) 🙂.
@jfriedenstab you do not need to wait for 8.6 to be released, since this repo has 2 projects in it. the docker-compose
folder with the images already targetting 8.6-alphaX, and the root-level docker-compose.yaml which points to the latest 8.5 release. your change only targets the one already targetting 8.6.
I am also testing this now.
@jfriedenstab you do not need to wait for 8.6 to be released, since this repo has 2 projects in it. the
docker-compose
folder with the images already targetting 8.6-alphaX, and the root-level docker-compose.yaml which points to the latest 8.5 release. your change only targets the one already targetting 8.6.
@jessesimpson36 Thanks for the explanation! This is more about the Web Modeler side though - we are not 100% certain yet if the feature will make it into 8.6
stable which is why we'd like to merge this PR only when we know more (probably next week Tuesday).
I see. Thanks for letting me know.
FYI: I just noticed that I used port 8080
instead of 18080
in the Keycloak URL (CAMUNDA_MODELER_CLUSTERS_0_OAUTH_URL
) and fixed it.
@jfriedenstab , what does it look like for it to be working? when I read the title of this PR, I would expect these things pre-filled, but this is what I get.
@jessesimpson36 That is because the cluster configuration is not yet used in the current alpha version of Web Modeler 🙂. The respective changes will only be ready (hopefully) in the 8.6.0 release (see also Wolfgang's comment above).
Alright, I misinterpreted the message about it being "fixed" after changing the port number.
Closes https://github.com/camunda/web-modeler/issues/10773