@<1822805241150574592:profile|ShinySparrow39> thanks for replying but i think you got me wrong. in your suggestion you can connect only files that are committed and pushed to git when running remotely, which is exactly what i'm trying to find a workaround to.

@<1523701070390366208:profile|CostlyOstrich36> Hi, i would expect a feature that looks something like this:
clearml Task CLI option "--mount-files" (or other informative name) which would be used to add local files to the sent task in the following format:

clearml-task --project examples --name remote_test --script my_script.py --mount-files "local_file_1:target_path_1, local_file_2:target_path_2"

of course there would be some size limit to the mounted files (same as you do with limiting uncommitted changes size).

needles to say that the expected behavior is to get a copy of the specified files in the specified target paths.
I think it is an easy to add feature and users could benefit quite a lot from it. what do you think?

Hi,
If your config file is a YAML or JSON or something similar, you can just connect it to your task using task.connect_configuration(dict) after loading it in your script. Then your full configuration can be seen in ClearML and retrieved in your script using task.get_configuration_object_as_dict()
see None

Hi @<1594863230964994048:profile|DangerousBee35> , I don't think there is such a mechanism currently. What would the expected/optimal behaviour would be in your use case?