conductor-oss / conductor-oss/conductor
[FEATURE]: when a workflow is removed, not all of its children are removed.
- Dominant language
- Java
- Stars
- 32.2k
- Forks
- 1k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 37
Description
Please read our [contributor guide](https://github.com/conductor-oss/conductor/blob/main/CONTRIBUTING.md) before creating an issue.
Also consider discussing your idea on the [discussion forum](https://github.com/conductor-oss/conductor/discussions) first.
## Describe the Feature Request
_When a workflow is removed, not all of its children are removed._
## Describe Preferred Solution
_You could include in the removal of a workflow the search for children via parent_workflow_id to then be able to remove them together with the connected tasks._
Contributor guide
Research direction
Start by tracing the workflow-removal entry point and the parent_workflow_id lookup described in the issue. Inspect how child workflows and their connected tasks are currently deleted, then add coverage showing that removing a parent also removes all children and connected tasks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100