Bug 748201

Summary: Ability to override Content Spec values from skynet client
Product: [Community] PressGang CCMS Reporter: Joshua Wulf <jwulf>
Component: CSProcessorAssignee: Lee Newson <lnewson>
Status: CLOSED CURRENTRELEASE 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: 2011-11-04 10:15:56 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-10-22 23:51:31 UTC 
The initial application is to override the Content Spec pubsnumber value, or to provide one when one was not supplied.

So,

skynet build 1 --override pubsnumber=2

Something like that.

Rational: every time that you want to stage a new version of a book it requires a unique pubsnumber. At the moment the way to do that is:

1. Build the book
2. Edit the Book_Info.xml file, update pubsnumber
3. Stage book

Once we implement https://bugzilla.redhat.com/show_bug.cgi?id=748199 it could be:

1. Pull the --post content spec
2. Edit the pubsnumber value
3. Push the updated content spec
4. Build
5. Stage

With the ability to override the pubsnumber, the process will be:

0. Check most recent pubsnumber on stage
1. Build with override pubsnumber++
2. Stage
Comment 1 Lee Newson 2011-10-24 05:55:58 UTC 
Done. We also allowed for the possibility of adding more parameters in the future.