Skip to content

[ISSUE][8.8] Duplicate Optimize Environment Variables in Configuration when running 'SM On-Demand OpenSearch 8.8+' job #4255

@matthewBearCamunda

Description

@matthewBearCamunda

Describe the issue:

The CAMUNDA_OPTIMIZE_ZEEBE_NAME and CAMUNDA_OPTIMIZE_OPENSEARCH_SETTINGS_INDEX_PREFIX appear twice in the Optimize configuration when running the SM On-Demand OpenSearch 8.8+ job

This was found during the investigation for camunda/camunda#35020

Actual behavior:

The CAMUNDA_OPTIMIZE_ZEEBE_NAME and CAMUNDA_OPTIMIZE_OPENSEARCH_SETTINGS_INDEX_PREFIX environment variables appear twice in the final pod configuration for Optimize

Expected behavior:

The CAMUNDA_OPTIMIZE_ZEEBE_NAME and CAMUNDA_OPTIMIZE_OPENSEARCH_SETTINGS_INDEX_PREFIX environment variables are used only once in the final pod configuration for Optimize

How to reproduce:

Image
  1. Create a new SM 8.8 Opensearch environment using this Github Action, and use the above inputs. For web modeler, you can use SNAPSHOT
  2. Once created, you can find the namespace of the created cluster in the Print outputs job in camunda platform gke -8.8
  3. Access the namespace and look at the Optimize configuration

Logs:

Environment:

Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

  • Platform:
  • Helm CLI version:
  • Chart version:
  • Values file:

Metadata

Metadata

Assignees

Labels

P2Moderate impact issues but not urgent for immediate resolution.kind/issueUnidentified issue, it could be a bug, misconfig, or anything in betweenplatform/awsIssues related to AWSplatform/gcpIssues related to GCPtarget:8.9Target release 8.9

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions