Wget failing with Scheme missing

[khrm]

Expected Behavior

wget should download to filename given.

Actual Behavior

[fetch-data : wget] --2023-04-04 01:02:34--  ht,....
[fetch-data : wget] Resolving api.npoint.io (api.npoint.io)... 216.24.57.253, 216.24.57.3
[fetch-data : wget] Connecting to api.npoint.io (api.npoint.io)|216.24.57.253|:443... connected.
[fetch-data : wget] HTTP request sent, awaiting response... 200 OK
[fetch-data : wget] Length: unspecified [application/json]
[fetch-data : wget] Saving to: 'e1ce697d6d9'
[fetch-data : wget] 
[fetch-data : wget]      0K                                                        27.7M=0s
[fetch-data : wget] 
[fetch-data : wget] 2023-04-04 01:02:35 (27.7 MB/s) - 'e1cea97d6d9' saved [274]
[fetch-data : wget] 
[fetch-data : wget] /workspace/wget-workspace/README.json: Scheme missing.
[fetch-data : wget] FINISHED --2023-04-04 01:02:35--
[fetch-data : wget] Total wall clock time: 1.0s
[fetch-data : wget] Downloaded: 1 files, 274 in 0s (27.7 MB/s)

Steps to Reproduce the Problem

1.

apiVersion: tekton.dev/v1beta1
kind: Pipeline
metadata:
  name: "demo-pipeline"
spec:
  params:
    - name: filename
      type: string
      description: The name of the file to be created
    - name: transform-path
      type: string
      description: The path of the transformed file
    - name: url
      type: string
  workspaces:
    - name: shared-workspace
  tasks:
    - name: fetch-data
      taskRef:
        name: wget
      workspaces:
        - name: wget-workspace
          workspace: shared-workspace
      params:
        - name: filename
          value: "$(params.filename)"
        - name: url
          value: "$(params.url)"

2. Create run

   
   apiVersion: tekton.dev/v1beta1
   kind: PipelineRun
   metadata:
   generateName: demo-pipeline-
   spec:
   pipelineRef:
   name: "demo-pipeline"
   params:
   - name: filename
     value: README.json
   - name: url
     value: https://api.npoint.io/sample
   workspaces:
   - name: shared-workspace
     volumeClaimTemplate:
       spec:
         accessModes:
           - ReadWriteOnce
         resources:
           requests:
             storage: 1Gi

Additional Info

[khrm]

/assign

[khrm]

/kind bug

[khrm]

So I think the documentation is wrong. That filename option is just to provide a new directory, not the filename.

[tekton-robot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale with a justification. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten with a justification. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen with a justification. Mark the issue as fresh with /remove-lifecycle rotten with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to [this](https://github.com/tektoncd/catalog/issues/1155#issuecomment-1702174544): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen` with a justification. >Mark the issue as fresh with `/remove-lifecycle rotten` with a justification. >If this issue should be exempted, mark the issue as frozen with `/lifecycle frozen` with a justification. > >/close > >Send feedback to [tektoncd/plumbing](https://github.com/tektoncd/plumbing). Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[Nold360]

This is still an issue... :(