The params in step are passed to stdoutConfig.path.

[cugykw]

Expected Behavior

In my taskrun resource, the params in spec and the params in step
have a variable with the same name. This can lead to unexpected behavior.

I've provided a simple example.

apiVersion: tekton.dev/v1alpha1
kind: StepAction
metadata:
  name: stepaction-demo
spec:
  params:
  - name: path
    type: string
  image: alpine
  workingDir: $(params.path)
  script: |
    env
    pwd
---
apiVersion: tekton.dev/v1
kind: TaskRun
metadata:
  name: step-action-example
spec:
  params:
  - name: path
    value: /home/work
  taskSpec:
    steps:
    - params:
      - name: path
        value: $(params.path)/app/demo
      ref: 
        name: stepaction-demo
      name: demo
      stdoutConfig: 
        path: $(params.path)/log

I hope the stdoutConfig.path value is '/home/work/log', but got
'/home/work/app/demo/log'.

The stdoutConfig in step should be replaced by params in taskrun,
but it is replaced by params in step.

Additional Info

tekton: 0.53.0

[cugykw]

/assign