Discrepancy in how --auth token is used

[golharam]

I'm testing this package out against arvados and am noticing an inconsistency with how the authorization token is being used.

I have the wes-server running and connected to Arvados with my Arvados token.

If I run wes-client,

wes-client --host=localhost:8080 --proto http --auth "Bearer my_arvados_token" --list

I see a list of runs. I then try

wes-client --host=localhost:8080 --proto http --auth "Bearer my_arvados_token" hello_world.cwl hello_world.input.yaml

but get the error:

ERROR:root:{'msg': "'Authorization' header is missing or empty, expecting Arvados API token", 'status_code': 401}
Traceback (most recent call last):
File "/scratch/workflow-service/workflow-service-env/bin/wes-client", line 8, in
sys.exit(main())
File "/scratch/workflow-service/wes_client/wes_client_main.py", line 130, in main
r = client.run(args.workflow_url, job_order, attachments)
File "/scratch/workflow-service/wes_client/util.py", line 287, in run
return wes_response(postresult)
File "/scratch/workflow-service/wes_client/util.py", line 214, in wes_response
raise Exception(error)
Exception: {'msg': "'Authorization' header is missing or empty, expecting Arvados API token", 'status_code': 401}

[golharam]

This is why:

workflow-service/wes_client/util.py

Line 285 in 962983a

# headers=self.auth,

the auth token is not passed in as part of the header, as its commented out.

[golharam]

If I uncomment that line, I get a follow up error:

Traceback (most recent call last):
File "/scratch/workflow-service/workflow-service-env/bin/wes-client", line 8, in
sys.exit(main())
File "/scratch/workflow-service/wes_client/wes_client_main.py", line 130, in main
r = client.run(args.workflow_url, job_order, attachments)
File "/scratch/workflow-service/wes_client/util.py", line 287, in run
return wes_response(postresult)
File "/scratch/workflow-service/wes_client/util.py", line 214, in wes_response
raise Exception(error)
Exception: {'msg': "'bytes' object has no attribute 'filename'", 'status_code': 500}

[golharam]

Looks like the cwl and input yaml need to be provided as attachments as well. Using what's in the README doesn't quite work, so I"m not entirely sure how this is supposed to work.

I tried using curl directly to figure out the parameters, but I'm missing something.