Switching to io.camunda:spring-boot-starter-camunda-sdk on SaaS doesn't pick up configuration

Camunda 8 Topics Discussion & Questions
1

Hi,

I updated to io.camunda:spring-boot-starter-camunda-sdk as documented on Spring Zeebe Getting Started.

I also added an application.yaml as documented

camunda:
  client:
    mode: saas
    auth:
      client-id: <your client id>
      client-secret: <your client secret>
    cluster-id: <your cluster id>
    region: <your cluster region>

However, the client is connecting to 0.0.0.0:26500

I debugged it a bit and it went through the class ZeebeClientConfigurationProperties which has a configuration-properties of “zeebe.client”. However, following configuration doesn’t work:

zeebe:
  cloud:
    cluster-id: <your cluster id>
    client-id: <your client id>
    client-secret: <your client secret>

However, this could be a fallback implementation.

Seems I’m mixing up something or either the implementation or documentation are not correct.

Who can clarify?

Maybe @jonathan.lukas ? :wink:

2

Hello @tobiasschaefer ,

the address should be taken from the CamundaClientProperties.

The other one is deprecated. I will test this myself tomorrow and let you know.

Jonathan

3

Hi @tobiasschaefer ,

I tried this on my own, however I am not able to reproduce the issue.

Could you please remove all legacy properties (and potentially environment variables) as the legacy configuration is applied if configured.

Hint for debugging: The zeebe client will use the grpcAddress() from the configuration interface rather than the gatewayAddress().

Thank you,
Jonathan

4

It’s intriguing to see how the transition to the SaaS model with Camunda is evolving the way we configure and interact with Zeebe! The convenience of a cloud-based solution offers so many advantages, but as you pointed out, it can lead to some configuration challenges. I’m curious if others have faced similar issues with the client not recognizing the SaaS settings. It would be interesting to hear any tips or workarounds people have found effective. Additionally, has anyone experimented with the latest features or integrations that come with this setup?

5

I mixed up some 8.5 and 8.6 dependencies and configurations.

What confused me was that the latest 8.5.x versions of the community project io.camunda.spring:spring-boot-starter-camunda used the new property structure while the newest io.camunda:spring-boot-starter-camunda-sdk 8.5.x version used the old structure.

Using 8.6.x consistently works as documented.

Thanks @jonathan.lukas for taking your time to check the issue.

1 Like
6

Hello @tobiasschaefer ,

sorry for the confusion. The community project evolved faster in that matter, so 8.5 is a bit difficult.

I am glad to hear that the consistent usage of 8.6 works as expected!

Best,
Jonathan

1 Like
7

Hello @jack456jokky ,

we have a guide available for getting started with our official sdk.

If there are any open questions after reading that guide, please open a thread and we will answer them in all details.

Best,
Jonathan

1 Like
8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.