we currently do not use execution expiration policies as we can not filter the executions which are supposed to be deleted. so far we only automatically delete successful workflows and keep the once with error for further manual investigation.
with this idea in mind we have to use the approach as described above and there seems to be only 2 solutions to this in my view:
1. add an option to "openstack workflow execution list" and/or "openstack workflow execution delete" that allows to only return root workflows.
2. create a new "mistral-db-manage" command that does allow the same filtering as in 1.)
please let me know if that now makes more sense to you or if you need some more information/discussion about the topic.
we currently do not use execution expiration policies as we can not filter the executions which are supposed to be deleted. so far we only automatically delete successful workflows and keep the once with error for further manual investigation.
with this idea in mind we have to use the approach as described above and there seems to be only 2 solutions to this in my view:
1. add an option to "openstack workflow execution list" and/or "openstack workflow execution delete" that allows to only return root workflows.
2. create a new "mistral-db-manage" command that does allow the same filtering as in 1.)
please let me know if that now makes more sense to you or if you need some more information/ discussion about the topic.