But looks like there is an issue with connecting to Operate according to the logs.
I recreated both the cluster and client credentials with the scope of Zeebe & Operate all over again to make sure those properties are configured properly.
What am I missing to make it work?
Should I add operate.client.profile?
If so, what value should I assign to it? (considering that I’m going with Camunda SaaS).
Logs
(I had to share it in GitHub Gists cause I exceeded the char limit for the post.)
Hi @MrDeeb - you can configure Operate credentials for SaaS in the application.properties file (see here), and that’s the first thing I would try. In the meantime, I’ve shared this post with our Education Team!
Hello there @MrDeeb, and thank you for your feedback.
I tested and found the root cause for your issue. During the course you need to download the connector-template-inbound which is using the connector version 8.7.0-alpha4 in the pom.xml file. This connector version requires a different configuration.
The course was developed for Camunda 8.5, so you can easily switch the connector version to 8.5.0 in the pom.xml properties and run the connector.
Please @VictorGarcia, when updating the course on Implementing Custom Inbound Connector, please, also include Linux OS path when mentioning the directory to watch for file creation, and deletion. Right now, only path for Windows and MacOS are specified. For me, on Linux, I have used - home/Download/Camunda