This message was deleted.

I know tasks are configured in the configuration phase and not in the execution phase. Actually, I could put info in some files, and uses thoses files as task input

Actually such "configuration tasks" that configure another task in their execution phase are simply possible. But they are bad practice and no longer possible if you care about the upcoming configuration cache which makes them illegal of course.

Right, but using a file would work and be less a bad practice right? I don’t know much about the Provider API, but is it possible to output a provider from a task and consume it in another task ?

Writing to a file is probably the cleanest solution, yes. Especially as only file outputs can properly be considered for up-to-date checks.