camunda-community-hub / camunda-community-hub/camunda-external-task-client-python3
Allow subscribing to a specific businessKey
- Dominant language
- Python
- Stars
- 81
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
Right now for when a worker is configured, it subscribes from all businessKeys for a list of topics.
I have a use case where there are multiple process instances running with different business keys.
This behavior is supported in the fetchAndLock REST call.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how worker configuration builds subscriptions and compare it with the fetchAndLock REST call, which already supports a specific businessKey. Define the expected behavior for a configured business key and verify that subscriptions no longer consume tasks from other business keys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100