You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 22, 2024. It is now read-only.
I have the Spring Boot Starter Camunda on my classpath and would like to disable zeebe (for a specific run mode). For doing so, I set camunda.client.zeebe.enabled=false property and management.health.zeebe.enabled=false property, so the auto configurations of the Zeebe client and its connection to Zeebe Cluster is disabled.
The Zeebe Event Lifecycle Producer still tries to inject the non-existing Zeebe client and fails:
***************************
APPLICATION FAILED TO START
***************************
Description:
Parameter 0 of method zeebeLifecycleEventProducer in io.camunda.zeebe.spring.client.CamundaAutoConfiguration required a bean of type 'io.camunda.zeebe.client.ZeebeClient' that could not be found.
Action:
Consider defining a bean of type 'io.camunda.zeebe.client.ZeebeClient' in your configuration.
I believe this is because the ZeebeCondition is ignored due to the second condition ( @ConditionalOnMissingBean(SpringZeebeTestContext.class)).
This makes it impossible to deactivate Zeebe by application properties.
As a workaround, I created a fake instance of the SpringZeebeTestContext:
I have the Spring Boot Starter Camunda on my classpath and would like to disable zeebe (for a specific run mode). For doing so, I set
camunda.client.zeebe.enabled=false
property andmanagement.health.zeebe.enabled=false
property, so the auto configurations of the Zeebe client and its connection to Zeebe Cluster is disabled.The Zeebe Event Lifecycle Producer still tries to inject the non-existing Zeebe client and fails:
I believe this is because the
ZeebeCondition
is ignored due to the second condition (@ConditionalOnMissingBean(SpringZeebeTestContext.class)
).This makes it impossible to deactivate Zeebe by application properties.
As a workaround, I created a fake instance of the
SpringZeebeTestContext
:This workaround helps because the condition is now satisfied.
See:
spring-zeebe/spring-boot-starter-camunda/src/main/java/io/camunda/zeebe/spring/client/CamundaAutoConfiguration.java
Line 50 in 588c8a9
The text was updated successfully, but these errors were encountered: