7.1.0-M15
Release 7.1.0-M15
You can consume all the Activiti artifacts for this release from Alfresco Nexus:
1
<repositories>
2
<repository>
3
<id>activiti-releases</id>
4
<url>https://artifacts.alfresco.com/nexus/content/repositories/activiti-releases</url>
5
</repository>
6
</repositories>
Copied!
Activiti Cloud:
1
<dependencyManagement>
2
<dependencies>
3
<dependency>
4
<groupId>org.activiti.cloud</groupId>
5
<artifactId>activiti-cloud-dependencies</artifactId>
6
<version>7.1.0-M15</version>
7
<scope>import</scope>
8
<type>pom</type>
9
</dependency>
10
</dependencies>
11
</dependencyManagement>
Copied!
Activiti Core
1
<dependencyManagement>
2
<dependencies>
3
<dependency>
4
<groupId>org.activiti</groupId>
5
<artifactId>activiti-dependencies</artifactId>
6
<version>7.1.0-M15</version>
7
<scope>import</scope>
8
<type>pom</type>
9
</dependency>
10
</dependencies>
11
</dependencyManagement>
Copied!

In the milestone 7.1.0-M15 you will find the following main fixes & features:

Changes from previous milestones

    Enhance Kafka Deployment Strategy by enabling dynamic scaling of the query consumer PODs: 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.
1
global:
2
messaging:
3
broker: kafka
4
partitioned: true
5
# global.messaging.partitionCount -- set the Kafka partition number
6
partitionCount: 4
7
activiti-cloud-query:
8
# replicaCount -- set the Kafka consumer number
9
replicaCount: 2
Copied!
    Use client/secret auth for Keycloak Admin Client: 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 keycloak client called (activiti-keycloak). As consenquence:
      The following mandatory properties has been added:
        activiti.keycloak.client-id=${ACT_KEYCLOAK_CLIENT_ID:activiti-keycloak}
        activiti.keycloak.client-secret=${ACT_KEYCLOAK_CLIENT_SECRET:}
      The following properties has been removed:
        activiti.keycloak.admin-client-app=${ACT_KEYCLOAK_CLIENT_APP:admin-cli}
        activiti.keycloak.client-user=${ACT_KEYCLOAK_CLIENT_USER:client}
        activiti.keycloak.client-password=${ACT_KEYCLOAK_CLIENT_PASSWORD:client}
Configuration with Helm charts:
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):
1
global:
2
keycloak:
3
clientSecret: changeit
Copied!
Or, if you prefer, you can use existing Activiti Keycloak Client Kubernetes secret by enablinguseExistingClientSecret:
1
kubectl create secret generic activiti-keycloak-client \
2
--from-literal=clientId=activiti-keycloak \
3
--from-literal=clientSecret=changeit
Copied!
1
global:
2
keycloak:
3
clientSecretName: activiti-keycloak-client
4
useExistingClientSecret: true
Copied!
Under the hood, the deployment will add the following environment variables to container specs:
1
specs:
2
containers:
3
- name: runtime-bundle
4
env:
5
- name: ACTIVITI_KEYCLOAK_CLIENT_ID
6
valueFrom:
7
secretKeyRef:
8
key: clientId
9
name: activiti-keycloak-secret
10
- name: ACTIVITI_KEYCLOAK_CLIENT_SECRET
11
valueFrom:
12
secretKeyRef:
13
key: clientSecret
14
name: activiti-keycloak-secret
Copied!
    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.
    Improve message event handling when there are several runtime bundles: 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:
    New default values starting from version 7.1.0-m15:
1
spring.cloud.stream.bindings.input.destination=messageEvents${activiti.cloud.messaging.destination-separator}${activiti.cloud.application.name}
2
spring.cloud.stream.bindings.output.destination=commandConsumer${activiti.cloud.messaging.destination-separator}${activiti.cloud.application.name}
3
spring.cloud.stream.bindings.commandConsumer.destination=${ACT_RB_COMMAND_CONSUMER_DEST:commandConsumer${activiti.cloud.messaging.destination-separator}${activiti.cloud.application.name}}
4
spring.cloud.stream.bindings.commandResults.destination=${ACT_RB_COMMAND_RESULTS_DEST:commandResults${activiti.cloud.messaging.destination-separator}${activiti.cloud.application.name}}
5
spring.cloud.stream.bindings.messageEvents.destination=messageEvents${activiti.cloud.messaging.destination-separator}${activiti.cloud.application.name}
Copied!
Previous default values:
1
spring.cloud.stream.bindings.input.destination=messageEvents
2
spring.cloud.stream.bindings.output.destination=commandConsumer
3
spring.cloud.stream.bindings.commandConsumer.destination=commandConsumer
4
spring.cloud.stream.bindings.commandResults.destination=commandResults
5
spring.cloud.stream.bindings.messageEvents.destination=messageEvents
Copied!
Last modified 10d ago