L3 - Default Context:
Currently Optimize requires at least one Camunda BPM engine to be configured to boot. However in the Camunda Cloud Optimize only depends on Elasticsearch. This restriction thus has to be removed.
AT:
- remove restriction that at least one Camunda BPM engine needs to be configured in Optimize
- make sure Optimize properly boots and the absence of a Camunda BPM engine does not cause any error logs or issues
- the readiness endpoint should return a 200 if there is no engine configured
This is the controller panel for Smart Panels app
[OPT-5280] Allow to configure no cambpm engine
| Description |
Original:
Context:
Currently Optimize requires at least one Camunda BPM engine to be configured. However in the Camunda Cloud Optimize only depends on Elasticsearch. This restriction thus has to be removed. AT: - remove restriction that at least one Camunda BPM engine needs to be configured in Optimize - make sure Optimize properly boots and the absence of a Camunda BPM engine does not cause any error logs or issues |
New:
Context:
Currently Optimize requires at least one Camunda BPM engine to be configured to boot. However in the Camunda Cloud Optimize only depends on Elasticsearch. This restriction thus has to be removed. AT: - remove restriction that at least one Camunda BPM engine needs to be configured in Optimize - make sure Optimize properly boots and the absence of a Camunda BPM engine does not cause any error logs or issues |
| Mentioned Roles |
| Mentioned Groups |
| Remote Link | New: This issue links to "Page (camunda confluence)" [ 16306 ] |
| Labels | Original: current_release must_have | New: must_have next_release |
| Description |
Original:
Context:
Currently Optimize requires at least one Camunda BPM engine to be configured to boot. However in the Camunda Cloud Optimize only depends on Elasticsearch. This restriction thus has to be removed. AT: - remove restriction that at least one Camunda BPM engine needs to be configured in Optimize - make sure Optimize properly boots and the absence of a Camunda BPM engine does not cause any error logs or issues |
New:
Context:
Currently Optimize requires at least one Camunda BPM engine to be configured to boot. However in the Camunda Cloud Optimize only depends on Elasticsearch. This restriction thus has to be removed. AT: - remove restriction that at least one Camunda BPM engine needs to be configured in Optimize - make sure Optimize properly boots and the absence of a Camunda BPM engine does not cause any error logs or issues - the readiness should return a 200 if there is no engine configured |
| Mentioned Roles |
| Mentioned Groups |
| Description |
Original:
Context:
Currently Optimize requires at least one Camunda BPM engine to be configured to boot. However in the Camunda Cloud Optimize only depends on Elasticsearch. This restriction thus has to be removed. AT: - remove restriction that at least one Camunda BPM engine needs to be configured in Optimize - make sure Optimize properly boots and the absence of a Camunda BPM engine does not cause any error logs or issues - the readiness should return a 200 if there is no engine configured |
New:
Context:
Currently Optimize requires at least one Camunda BPM engine to be configured to boot. However in the Camunda Cloud Optimize only depends on Elasticsearch. This restriction thus has to be removed. AT: - remove restriction that at least one Camunda BPM engine needs to be configured in Optimize - make sure Optimize properly boots and the absence of a Camunda BPM engine does not cause any error logs or issues - the readiness endpoint should return a 200 if there is no engine configured |
| Mentioned Roles |
| Mentioned Groups |