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] Execution Identity integration - iteration 2 #2294

Closed
2 tasks done
Tracked by #803
drodriguez-305 opened this issue Sep 4, 2024 · 6 comments · Fixed by #2476
Closed
2 tasks done
Tracked by #803

[ENHANCEMENT] Execution Identity integration - iteration 2 #2294

drodriguez-305 opened this issue Sep 4, 2024 · 6 comments · Fixed by #2476
Assignees
Labels
cycle/alpha1 Tasks will be done in alpha1 cycle kind/enhancement New feature or request priority/important Must be worked on either currently, or very soon, ideally in time for the next release.

Comments

@drodriguez-305
Copy link
Contributor

drodriguez-305 commented Sep 4, 2024

Describe the use case:

This feature request is about integrating the execution layer identity into a SM cluster. Execution Identity is a new component that is part of the mono-repo https://github.com/camunda/camunda and will be the component to manager uses/authorizations within a cluster going forward and replace the current present identity component.

For more context, also see https://docs.google.com/presentation/d/1VcdJGDqX4Jcjt7w2gf7KvEyLUueHojmg4wxfcZPJoDI/edit#slide=id.g21c05d33edd_0_0

relates to https://github.com/camunda/product-hub/issues/2222

first iteration was completed #2195
Describe the enhancement/feature:

Iteration 2 - Webapp Exporter

Iteration 3- Migration App - TBD by @Ben-Sheppard

No tasks being tracked yet.
@drodriguez-305 drodriguez-305 added kind/enhancement New feature or request priority/important Must be worked on either currently, or very soon, ideally in time for the next release. labels Sep 4, 2024
@aabouzaid aabouzaid added this to the 8.7 Release Cycle milestone Sep 9, 2024
@megglos
Copy link
Contributor

megglos commented Oct 2, 2024

@mustafadagher can you please provide a minimal elasticsearch and opensearch config for the camunda exporter here to get this integration started?

As a minimum, let's take the current elasticsearch exporter config as orientation + whatever is necessary from you perspective for the new exporter.

@mustafadagher
Copy link

mustafadagher commented Oct 9, 2024

@megglos
To configure the new camunda exporter,

Under the following

zeebe:
      broker:
        exporters:

We should add:

          camundaExporter:
            className: "io.camunda.exporter.CamundaExporter"
            args:
              connect:
                type:
                url: 
                username:
              index:
                prefix: 
              retention:
                enabled: true
                minimumAge: 
                policyName:
              createSchema: true 

Notice that connect.type should have a value one of elasticsearch or opensearch. Also this is just a minimal configuration, a lot more can be configured based of ExporterConfiguration class

@megglos
Copy link
Contributor

megglos commented Oct 9, 2024

@drodriguez-305 @aabouzaid can you take this from here to enable the new exporter in the helm chart for 8.7.0-SNAPSHOT setups? We need this ready for the upcoming 8.7.0-alpha1 by Oct 28th. (Code Freeze)

@ChrisKujawa
Copy link
Member

@drodriguez-305 was this closed on purpose?

@ChrisKujawa
Copy link
Member

@drodriguez-305 @aabouzaid we need for Identity + Camunda Exporter the migration application for alpha2 - is this on your radar?

@drodriguez-305
Copy link
Contributor Author

Hey @Zelldon after speaking with @aabouzaid we are creating a new issue for Identity + Camunda Exporter migration application for alpha2 and will be closing this one.

The new issue created #2574

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cycle/alpha1 Tasks will be done in alpha1 cycle kind/enhancement New feature or request priority/important Must be worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants