Bug 766257

Summary: skynet client: push with specified server and apikey does not work
Product: [Community] PressGang CCMS Reporter: Joshua Wulf <jwulf>
Component: CSProcessorAssignee: Lee Newson <lnewson>
Status: CLOSED NOTABUG QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.xCC: jwulf, lcarlon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-20 01:44:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Joshua Wulf 2011-12-11 11:03:07 UTC 
[jwulf@gaura csprocessor-data.sql]$ skynet push -s skynet.bne.redhat.com:8180 -a 108108 -cn ~/Work/EDS/EDS\ GSG-spec

Error: Invalid argument!

java -jar skynet.jar push [OPTIONS] [FILENAME]
  OPTIONS:
    --contentspec, -c
    --edit, -e
    --exec-time
    --new, -n
    --permissive, -p
    --tagsmap, -T

  FILENAME - The name/location of the file to be uploaded.
--------------------------------------------------------------------------
That should work.

Current Workaround:

Put the server and apikey information into ~/.config/skynet-ws/skynet.ini and use:

skynet push --config ~/.config/skynet-ws ~/Work/EDS/EDS\ GSG-spec
Comment 1 Lee Newson 2012-01-05 23:21:10 UTC 
Tested with build 0.16.0 of the client. The parameter -s is for snapshots, to specify the server path you need to use a capital S. I may have forgotten to change the symbol in older versions of the client help file, however I'm unable to check since I no longer have access to the older versions. The symbol used to be -s however it was changed to a capital when snapshots were added.