Yota Hamada

Hi @kimkit, I think your idea sounds really interesting! I'd love to hear more about it. Can you let me know what kind of executor you need? If you're looking...

Hi @kimkit , I was thinking that you might be able to call the binary in a workflow like this: ```yaml steps: - name: run-script command: lua-runner script: | ```...

Great to hear that. Thanks.

It's already possible by creating a script that watches a file to be created, still, it's great to have it as a feature. PR for this would be appreciated.

Hello, thanks for the question. I tried the same DAG on my local computer and it seems working fine. Would you mind share the Dagu version are you using? 

Thanks for letting me know! Internally, Dagu works this way: 1. write the script to an arbitrary temp file. 2. execute the command passing the temp file as the single...

Hi Oliver, thanks for your thorough investigation and the great suggestion! You're right about the "internal/schedule/node", it is responsible for creating a tempfile. > Maybe it will be a good...

Thanks for the great suggestion. Yes, as you mentioned there're two different approaches to dealing with the issue. I think calling other DAGs (or sub-DAGs) natively looks like a good...

Not yet. While importing steps or calling other DAGs to avoid copy/paste between DAGs is an interesting idea, I think that allowing the direct importing of other DAGs in YAML...

my idea: ``` steps: - sub_workflow1 run: path/to/sub_workflow.yaml params: "A=1 B=2" ```