May 2023 (#120)

* Manage when type change in a worker/connector

* first version

* prepare synchronization

* manage changement in type (update correctly the database)

* docker-compose is working

* Test docker compose items

* Test docker compose items

* Fix orthography errors

* Different fix in May

---------

Co-authored-by: Dave Paroulek <[email protected]>

README.md

@@ -102,11 +102,24 @@ Because the library contains Java and React script, to deploy it, the machine mu
 
 CI=false, else any warning will stop the construction
 
-Docker image is then availabe in the package
+Docker image is then available in the package
 `https://github.com/camunda-community-hub/zeebe-cherry-runtime/pkgs/container/zeebe-cherry-runtime`
 
 
 
 
 
+# Build
+The project is configured to publish automatically to maven central the JAR file, and to docker package a Docker image
 
+## Maven Central repository
+
+See .github/workflows/mvn-release.yml
+
+
+Visit
+https://github.com/camunda-community-hub/community-action-maven-release/tree/main
+
+
+Error
+Error: Resource not accessible by integration

docker-cherry/.env

@@ -0,0 +1,21 @@
+## Image versions ##
+CAMUNDA_CONNECTORS_VERSION=0.19.1
+CAMUNDA_OPTIMIZE_VERSION=3.10.0
+CAMUNDA_PLATFORM_VERSION=8.2.4
+CAMUNDA_WEB_MODELER_VERSION=8.2.2
+ELASTIC_VERSION=7.17.9
+KEYCLOAK_SERVER_VERSION=19.0.3
+MAILPIT_VERSION=v1.5.4
+POSTGRES_VERSION=14.5-alpine
+HOST=localhost
+
+## Configuration ##
+# By default the zeebe api is public, when setting this to `identity` a valid zeebe client token is required
+ZEEBE_AUTHENTICATION_MODE=none
+ZEEBE_CLIENT_ID=zeebe
+ZEEBE_CLIENT_SECRET=zecret
+
+# Set to 'true' to enable resource based authorizations for users and groups
+# This can be used to limit access for users or groups to view/update specific
+# processes and decisions in Operate and Tasklist
+RESOURCE_AUTHORIZATIONS_ENABLED=false

docker-cherry/README.md

@@ -0,0 +1,36 @@
+# Docker compose
+
+This section shows different docker compose example. Feel free to copy and adapt them to your use case
+
+There is two flavor:
+* the default one, using a H2 database
+* the post
+
+## H2 database
+
+Start a complete cherry plus zeebe platform
+
+```shell
+docker-compose -f docker-compose-core.yaml -f docker-compose-cherry.yaml up -d 
+```
+
+To remove the different container created (use `stop` instead of `down` if you just want to stop and don't remove the container)
+
+```shell
+docker-compose -f docker-compose-core.yaml -f docker-compose-cherry.yaml down -v
+```
+
+
+## Postgres
+
+This example used a postgres database to store information (statistics, upload connectors)
+
+```shell
+docker-compose -f docker-compose-core.yaml -f docker-compose-cherry-postgres.yaml up -d 
+```
+
+To remove the different container created (use `stop` instead of `down` if you just want to stop and don't remove the container)
+
+```shell
+docker-compose -f docker-compose-core.yaml -f docker-compose-cherry-postgres.yaml down -v
+```

docker-cherry/connector-secrets.txt

@@ -0,0 +1,2 @@
+# add secrets per line in the format NAME=VALUE
+# WARNING: ensure not to commit changes to this file

docker-cherry/docker-compose-postgres.yml → docker-cherry/docker-compose-cherry-postgres.yaml

@@ -1,27 +1,28 @@
 version: "3"
 services:
 
-# Attention, this configuration is not validated
   cherry-runtime:
-    image: docker pull ghcr.io/camunda-community-hub/zeebe-cherry-runtime:latest
+    image: ghcr.io/camunda-community-hub/zeebe-cherry-runtime:latest
     container_name: cherryruntime
     ports:
       - "9081:9081"
     environment:
-      - ZEEBE_CLIENT_BROKER_GATEWAY_ADDRESS=host.docker.internal:26500
+      - ZEEBE_CLIENT_BROKER_GATEWAY_ADDRESS=zeebe:26500
       - ZEEBE_CLIENT_SECURITY_PLAINTEXT=true
-      - ZEEBE_CLIENT_CLOUD_REGION=
-      - ZEEBE_CLIENT_CLOUD_CLUSTERID=
-      - ZEEBE_CLIENT_CLOUD_CLIENTID=
-      - ZEEBE_CLIENT_CLOUD_CLIENTSECRET=
+#      - ZEEBE_CLIENT_CLOUD_REGION=
+#      - ZEEBE_CLIENT_CLOUD_CLUSTERID=
+#      - ZEEBE_CLIENT_CLOUD_CLIENTID=
+#      - ZEEBE_CLIENT_CLOUD_CLIENTSECRET=
       - LOGGING_LEVEL_ROOT=INFO
+      - spring.profiles.active=postgres
       - spring.datasource.url=jdbc:postgresql://postgres/cherrydb
       - spring.datasource.username=camunda
       - spring.datasource.password=camundapassword
-      - spring.datasource.driver-class-name=org.postgresql.Driver
-      - spring.datasource.spring.jpa.database-platform=org.hibernate.dialect.PostgreSQL94Dialect
-      - spring.datasource.org.hibernate.dialect=org.hibernate.dialect.PostgreSQL94Dialect
+
+    networks:
+      - camunda-platform
     depends_on:
+      - zeebe
       - postgres
 
   postgres: # https://hub.docker.com/_/postgres
@@ -40,3 +41,8 @@ services:
       interval: 10s
       timeout: 5s
       retries: 5
+    networks:
+      - camunda-platform
+
+networks:
+  camunda-platform:

docker-cherry/docker-compose-cherry.yaml

@@ -0,0 +1,23 @@
+version: "3"
+services:
+
+  cherryruntime:
+    image: ghcr.io/camunda-community-hub/zeebe-cherry-runtime:latest
+    container_name: cherryruntime
+    ports:
+      - "9081:9081"
+    environment:
+      - ZEEBE_CLIENT_BROKER_GATEWAY_ADDRESS=zeebe:26500
+      - ZEEBE_CLIENT_SECURITY_PLAINTEXT=true
+#      - ZEEBE_CLIENT_CLOUD_REGION=
+#      - ZEEBE_CLIENT_CLOUD_CLUSTERID=
+#      - ZEEBE_CLIENT_CLOUD_CLIENTID=
+#      - ZEEBE_CLIENT_CLOUD_CLIENTSECRET=
+      - LOGGING_LEVEL_ROOT=INFO
+    networks:
+      - camunda-platform
+    depends_on:
+      - zeebe
+
+networks:
+  camunda-platform: