[Bug]: InputData parameter is not resolved for transformations with input data

[arrabito]

Search before creating an issue

• I have searched existing issues and confirmed this is not a duplicate

Bug Description

While in the job JDL of jobs created by transformations the InputData parameter seems to be set:

  Arguments = "jobDescription.xml -o LogLevel=INFO  -p JOB_ID=00000001  -p InputData=/ctao/user/a/arrabito/test_ts/data_001.txt";

  Parameter.InputData = "/ctao/user/a/arrabito/test_ts/data_001.txt";

it's not dynamically resolved when used in job.setExecutable, e.g.:

job.setExecutable("/bin/echo", arguments = "@{InputData}")

Is this wanted or is it a bug?

I attach here a script to reproduce the issue.

The std output of the echo command being empty:

`

test_ts.py

`

Steps to Reproduce

No response

Expected Behavior

No response

Actual Behavior

No response

Environment

No response

Relevant Log Output

Additional Context

No response

[arrabito]

I've investigated a little bit and I'm wondering if for some reason this behaviour is wanted as I see here

this condition:

        for paramName, paramValue in paramsDict.items():
            if paramName not in ("InputData", "Site", "TargetSE"):
                if paramValue:
                    self._logVerbose(f"Setting {paramName} to {paramValue}", transID=transID, method=method)
                    seqDict[paramName] = paramValue

Just to let you know that I've tried to remove InputData from the list in the snippet above and also applied some other changes to the WorkflowTasks.py and I've been almost able to find a solution, but not totally working.

I haven't investigated futher, but I can share my modifications here if it could be useful, but maybe you get to the fix quicker.