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.

Sign up for GitHub

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

Jump to bottom

Remove the Operate client dependency #3637

Open
chillleader opened this issue Nov 12, 2024 · 2 comments · May be fixed by #3638
Open

Remove the Operate client dependency #3637

chillleader opened this issue Nov 12, 2024 · 2 comments · May be fixed by #3638
Assignees
@chillleader
Labels
kind:task Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc.

Comments

@chillleader
Copy link
Member

What should we do?

As part of the C8 REST API, new endpoints are being introduced that can fully replace our Operate API use-cases (specifically, process definition querying, getting the process XML and so on).

The new query endpoints can be accessed natively through the Zeebe client. Therefore we can get rid of the Operate client dependency and just use the Zeebe client for all our needs.

Query endpoints are disabled by default as they are still in the alpha state, but the plan is to make them generally available by 8.7: camunda/camunda#20579

Why should we do it?

This will simplify our setup and configuration the users have to do. Also the Operate API will be on deprecation path in the future.
@chillleader chillleader added the kind:task Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc. label Nov 12, 2024
@chillleader chillleader self-assigned this Nov 12, 2024
@chillleader chillleader linked a pull request Nov 12, 2024 that will close this issue
Open
1 task
@chillleader
Copy link
Member Author

I created a draft PR with the necessary changes: #3638

@chillleader
Copy link
Member Author

Found a bug in the REST API client that blocks this activity: camunda/camunda#24779

I was able to apply an ad-hoc fix locally but before merging the PR it would be cool to have it fixed in the client.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chillleader chillleader

Labels
kind:task Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore(deps): remove operate client camunda/connectors
1 participant
@chillleader