Tommy Li
Tommy Li
I think there are some test cases for the `spec.steps.*.script`, but not for `params`. https://github.com/tektoncd/pipeline/blob/main/examples/v1alpha1/taskruns/step-script.yaml#L102-L118
```yaml taskSpec: steps: - name: main command: - sh - -c - | set -e echo $0 echo $1 echo $2 - $(inputs.params.msg1) - $(inputs.params.msg2) - $(inputs.params.msg3) image: alpine:3.6 ```...
Yes that make sense to me.
We should add this `AuthorizationPolicy` to the Kubeflow manifests because Kubeflow 1.4 still has this issue.
@C1berwiz I'm not sure do we want to host a big binary file like [rfmodel.pickle](https://github.com/kserve/kserve/pull/2355/files#diff-cecaba4f0caa00d6cbe43637c9043bc9ce59a4bd08c466e9977f85d21a239a31) in the KServe repo. Usually we either provide a simple script to train the model...
cc @yhwang @rimolive
related: https://github.com/tektoncd/pipeline/issues/6483
KFP-Tekton is licensed under [Apache 2.0](https://github.com/kubeflow/kfp-tekton/blob/master/LICENSE).