global:
messaging:
broker: kafka
partitioned: true
# global.messaging.partitionCount -- set the Kafka partition number
partitionCount: 4
activiti-cloud-query:
# replicaCount -- set the Kafka consumer number
replicaCount: 2
The following mandatory properties has been added:
It's possible to create a default Activiti Keycloak Client Kubernetes secret with Helm by using the following values (replace changeit by the secret of your choice):
global:
keycloak:
clientSecret: changeit
Or, if you prefer, you can use existing Activiti Keycloak Client Kubernetes secret by enablinguseExistingClientSecret:
Removal of activiti-cloud-services-common-identity-keycloak from connector starter: activiti-cloud-starter-connector is no longer bringing the depencency toactiviti-cloud-services-common-identity-keycloak, please add it explicitly in the case where your connector implementation was rellying on it.
New default values starting from version 7.1.0-m15:
In the milestone 7.1.0-M15 you will find the following :
: previously, while using partioned message streams, the property partitionCount was used to define at the same time the number of partitions and the number of replicas for query service for both RabbitMQ and Kafka binders. However, Kafka binder supports dynamically scaling and one replica can handle more than one partition. Starting from version 7.1.0-M15 the number of partitions and the number of replica for query service are set independently while using Kafka binder: partitionCount is used to define the number of partions and replicaCount is used to define the number of replicas for query service.partitionCount should be greater than or equals to replicaCount.
: previously, in order to retrieve users and groups from Keycloak, Activiti Cloud used to connect using the credentials (username/password) of a special user called client that was added to the Realm. Starting from the version 7.1.0-M15 the user client was removed in favor of a new called (activiti-keycloak). As consenquence:
: by default, binding destinations related to BPMN Messages are now scoped by Activiti Cloud Application. This allow having more than one Runtime Bundle using the same message broker. This change should be transparent for most of the users, but here are the changes performed: