Discrepancy in how --auth token is used

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}