v0.0.5

What's Changed

• Fix Kafka-based communication:
  • User group-id properly
  • Filter messages according to the tenant-id
  • Only log unprocessed messages not filtered by tenant-id
  • Breaking change: Adopt application.yaml configuration of Kafka-based communication (details below)

Full Changelog: 0.0.4...0.0.5

Breaking changes

Change your application.yaml configuration for Kafka-based communication

The group-id-suffix property has to be set. It is used as a suffix for the Kafka client's group-id. It has to identify the application as a whole, not a particular installation (e.g. pod in Kubernetes). Examples:

• local used for a developer's local setup
• bc used for the business cockpit
• my-awesome-workflow-container used for a Spring Boot container hosting several workflow modules

1. application.yaml of business cockpit Spring Boot container:

   Before 0.0.5:

   bpms-api:
     kafka-topics:
       workflow: "workflows"
       user-task: "user-tasks"
       workflow-module: "modules"

   Using 0.0.5:

   bpms-api:
     kafka:
       group-id-suffix: local
       topics:
         workflow: "workflows"
         user-task: "user-tasks"
         workflow-module: "modules"

2. application.yaml of Spring Boot container hosting workflow modules:

   Before 0.0.5:

   vanillabp:  
     cockpit:  
       kafka:  
         user-task-topic: user-tasks
         workflow-topic: workflows
         workflow-module-topic: modules

   Using 0.0.5:

   vanillabp:  
     cockpit:
       kafka:
         group-id-suffix: local
         topics:
           workflow: "workflows"
           user-task: "user-tasks"
           workflow-module: "modules"