Summary
Tested against: Conductor OSS 3.32.0-rc.9
The Conductor server has a NOOP system task type (TaskType.NOOP) that
completes immediately with no inputParameters. The Python SDK has neither an
enum value nor a builder class for it.
Details
from conductor.client.workflow.task.task_type import TaskType
hasattr(TaskType, "NOOP") # False
There is no noop_task.py and no NoopTask class anywhere in the SDK.
NOOP is useful as an explicit no-op placeholder in workflow branches (e.g.
the default branch of a SWITCH where nothing should happen). Without SDK support,
users must use raw dicts.
Suggested fix
Add to task_type.py:
Add src/conductor/client/workflow/task/noop_task.py:
class NoopTask(TaskInterface):
def __init__(self, task_ref_name: str):
super().__init__(task_reference_name=task_ref_name,
task_type=TaskType.NOOP)
Verified against
Conductor server 3.32.0-rc.9. A raw-dict NOOP workflow registered and ran
to COMPLETED on the server. Only the SDK support is missing.
Summary
Tested against: Conductor OSS 3.32.0-rc.9
The Conductor server has a
NOOPsystem task type (TaskType.NOOP) thatcompletes immediately with no inputParameters. The Python SDK has neither an
enum value nor a builder class for it.
Details
There is no
noop_task.pyand noNoopTaskclass anywhere in the SDK.NOOP is useful as an explicit no-op placeholder in workflow branches (e.g.
the default branch of a SWITCH where nothing should happen). Without SDK support,
users must use raw dicts.
Suggested fix
Add to
task_type.py:Add
src/conductor/client/workflow/task/noop_task.py:Verified against
Conductor server 3.32.0-rc.9. A raw-dict NOOP workflow registered and ran
to
COMPLETEDon the server. Only the SDK support is missing.