-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow Embedded Engine to be configured with configuration file #32
Comments
@RomanJRW thanks for sharing. Most of the configuration in Zeebe is related to the distributed system or other parts that EZE (as a pure workflow engine) doesn't have. Please list all properties that you would like to configure. |
I think everything we care about is ES exporter related. The partition count is not part of exporter configuration, but for us it's only important because we import the data by partition, so need to test with multiple configured. See below for the current state of our configuration file for ITs:
|
Optimize currently uses the EmbeddedBrokerRule, and its constuctor makes things very easy for us to apply our quite simple config as follows:
The most important config for us is the ElasticsearchExporter we use, but we also set the number of partitions (2) too.
If possible, an equivalent for EZE would be very helpful. I understand that this may be currently possible using a parameter map, but this is a bit more awkward for us to use. We would eventually like to use the JUnit 5 extension too, and I don't think this is currently an option with that.
The text was updated successfully, but these errors were encountered: