I'm not sure about the intended use of

connect_configuration

now.

Basically here is the rationale behind it:
I have a config file that I want to log on the Task, and I Also want to be able to change this configuration file externally when launching using an agent (i.e. edit the content) I have a nested dictionary that I do not want to flatten and push as hyper-parameters because it is not very readble, so I want to store it in a more human readable form and edit it as config file

...

Task.set_configuration_object

, etc.

Basically do not call set_configuration_object directly, instead use connect_configuration. The main difference is that "connect" as a concept is a two way conneciton, when runnign manually log on the Task/backend, when running via agent, get the values from the Task/backend into the code. set_xyz calls are always setting the Task's/backend value
Make sense ?