Releases: camunda-community-hub/pyzeebe
Releases · camunda-community-hub/pyzeebe
v2.0.1
Fixed:
TaskDecorator
andZeebeTaskRouter
not being in exports
v2.0.0
v2.2.0
Using decorators instead of classes to create tasks
Changes
- Added ability to create task using decorator:
@worker.task()
- Added class called
ZeebeTaskRouter
which should help organize projects - Renamed
TaskContext
toJob
- Merged
TaskStatusController
functionality into the newJob
class - Removed
Task
from standard imports because of decorator
API Changes
External updates:
- Renamed
TaskContext
toJob
- Merged
TaskStatusController
functionality into the newJob
class - Renamed
TaskStatus
toJobStatus
- Moved
stop_event
fromwork
internally, so users don't have to importthreading.Event
- Added
stop
function toZeebeWorker
which now uses the internalthreading.Event
- Renamed
add_task
to_add_task
- Added class
ZeebeTaskRouter
which inherits fromZeebeTaskHandler
. This class allows splitting tasks into multiple files (like fastapi'sAPIRouter
) - Added
include_router
toZeebeWorker
which allows aZeebeWorker
instance to absorb aZeebeTaskRouter
's tasks - Added
ExceptionHandler
for ease of use - Added optional
message_id
parameter topublish_message
inZeebeClient
v1.2.3
v1.2.2
Enhancements:
- Moved test files to
tests
- No test files in published package
- Coverage more accurate
v1.2.1
Fixed:
- Tasks failing because of decorators
v1.2.0
Added:
- Secure connection options:
- TLS
- OAuth2
- Camunda Cloud
Fixed
- Worker not working without stop event
v1.1.2
v1.1.1
v1.1.0
Added:
- Client functionality:
- Run workflow
- Run workflow with result (await workflow result)
- Cancel running workflow instances
- Deploy workflow definition file (bpmn/yaml)
- Publish messages
- Self defined grpc exceptions
- Integration tests against zeebe
v1.0.1
Fixed
- Worker stopping on startup
- Connection to zeebe default parameters not working
- Tasks not activating jobs concurrently