Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support easy Camunda Cloud configuration

See original GitHub issue

The latest version 0.7.1 doesn’t seem to support Camunda Cloud out of the box. According to the readme, it is only possible to configure The configuration of a client id and a client secret is not possible.

The #67 should make it possible to add a credentials provider. Nevertheless, it would nice to support Camunda Cloud with less effort. For example:

      contactPoint: "Camunda Cloud Contact Point"
    id: "Camunda Cloud Client ID"
    secret: "Camunda Cloud Client Secret"

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:1
  • Comments:8 (8 by maintainers)

github_iconTop GitHub Comments

salaboycommented, Dec 10, 2019

@ArtunSubasi that sounds like a great community contribution, I don’t mind helping, reviewing and testing a PR if you create one. We can definitely create a release before the end of the year if we have that fix in place . I totally agree with you on the fact that it should be just those three properties to get it working with cloud

berndrueckercommented, Apr 7, 2020

Sorry - I overlooked that. That looks basically good to me (I did a quick and dirty version here

So the discussion is

Then I found out that the Camunda Cloud connections work out-of-the-box using environment variables. Therefore, I don’t think it is a good idea to add additional support for the application properties. Since the credentials contain confidential information, they must be encrypted or injected using the environment variables anyway.

Any opinions? @ArtunSubasi @salaboy

My personal opinion is that it would still be valuable to have it via Spring Boot - which also allows you to easily set environment variables. It is simply more aligned with the Spring Boot way - or WDYT?

And I am the only one that likes to put some defaults simply in the application.yaml and get going to play around locally? Environment variables are an obstacle in that worfklow. WDYT?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Support easy Camunda Cloud configuration · Issue #81 - GitHub
The latest version 0.7.1 doesn't seem to support Camunda Cloud out of the box. According to the readme, it is only possible to...
Read more >
Zeebe on Camunda Cloud: Getting Started
Zeebe is now available as a managed service in the Camunda Cloud. This post is a guide to getting started with the Zeebe...
Read more >
Installation | Camunda Platform 8 Docs
This document describes the installation process of the Camunda Optimize and connect it to a Camunda 7 stack, as well as various configuration...
Read more >
Getting started with Camunda Cloud and Spring Boot - YouTube
Deploy a self-managed Zeebe Cluster using Kubernetes KIND · Testing processes for Camunda Cloud and Zeebe · Building a Camunda Platform 7 Project ......
Read more >
Tutorial: How to Send an Email Worker Using Camunda Cloud ...
Camunda Platform 8, our cloud -native solution for process orchestration, launched in April 2022. Images and supporting documentation in this ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found