Bug 499161

Summary: expose Spacewalk behavior via a CLI
Product: [Community] Spacewalk Reporter: Jesus M. Rodriguez <jesusr>
Component: APIAssignee: Miroslav Suchý <msuchy>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Satellite QA List <satellite-qa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 0.6CC: mmccune, msuchy
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-10 12:00:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 456554    

Description Jesus M. Rodriguez 2009-05-05 13:43:52 UTC
The Spacewalk API has been enhanced with each release of Spacewalk:

What would be great is to have a CLI to interact with the Spacewalk server something along the lines of:

spacewalk user create --login=foo@redhat.com
spacewalk channel create --name="RHEL 5 i386" --arch=i386 --label=rhel5-i386
spacewalk kickstart create --name=rhel5-i386 --channel=rhel5-i386
spacewalk activationkey create --name=rhel5-i386 --channel=rhel5-i386

and so on .. would be immensely useful.  Just because our GUI is large 
and has many many different things to manage that doesn't mean there are 
simple entry points to all the common objects in Satellite.

The above could just be an interface to our existing XMLRPC API, all the 
above and more is available to be called to without our GUI.  The only 
thing we are lacking is an implementation of the actual CLI bits.

Comment 1 Miroslav Suchý 2009-07-22 09:36:45 UTC
Done in commit:
The new script is call spacewalk-api and is in package spacewalk-utils

Comment 2 Miroslav Suchý 2009-09-10 12:00:53 UTC
Spacewalk 0.6 released.