Skip to content
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

[ENHANCEMENT] simpler Optimize configuration (when using custom Elasticsearch index prefix) #2111

Open
bbakker2 opened this issue Jul 3, 2024 · 1 comment
Labels
kind/enhancement New feature or request

Comments

@bbakker2
Copy link

bbakker2 commented Jul 3, 2024

Describe the use case:

We use custom Elasticsearch index prefixes. The helm chart does not provide properties to set the zeebe-record or the optimize index prefixes.
Optimize also does not appear to support the springboot configuration mechanism to override configuration keys with environment variables, like Operate and Tasklist do.
Consequently we have to put the configuration in optimize.configuration. This adds redundancy to the helm values.yaml and exposes Optimize configuration internals (e.g. like having to set spring.profiles.active: ccsm

Describe the enhancement/feature:
Either add helm chart values for Optimize for config options.

  • zeebe.name. Even better: let it use global.elasticsearch.prefix as default.
  • es.settings.index.prefix

or add support for environment variable based configuration overrides to Optimize.

Additionally, for consistency it would be great to have optimize use zeebe.partitionCount instead of having to configure it manually.

You can configure Optimize without having to specify the full optimize.configuration.

@bbakker2 bbakker2 added the kind/enhancement New feature or request label Jul 3, 2024
@aabouzaid
Copy link
Member

It will be fixed by #2186

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants