Hi @MarcelWilhelmi 👋🏻

For now, it's not possible but the suggestion can be an interesting feature, I'm not sure about the syntax:

scheduler_bundle:
    transport:
        dsn: '...'
    tasks:
        my-first-task:
            type: 'command'
            command: '...'
        import:
            my_tasks_1.yaml
            my_tasks_2.yaml

This seems weird as the import key can be the one used to create a new task, maybe we could use it but add it as a special meaning in the configuration (thanks to normalization).

Regarding the import key from the DIC, the behaviour is normal as it's a special key used in the DIC configuration 🙂

Hi @Guikingone,
I agree. The syntax is not perfect, it was just an example. There are definitely better alternatives :-)