Bug 788014

Summary:	RFE: csprocessor checkout command
Product:	[Community] PressGang CCMS	Reporter:	Joshua Wulf <jwulf>
Component:	CSProcessor	Assignee:	Lee Newson <lnewson>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.x	CC:	jwulf, lcarlon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	0.22.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-20 01:46:52 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	796009

Description Joshua Wulf 2012-02-07 08:45:16 UTC

Add an option for the csprocessor to create a csprocessor.cfg file.

It shouldn't do it all the time, because someone might pull a bunch of specs in the same place.

But there should be a total end-to-end workflow like this:

1. csprocessor pull -cf 14
Note: defaults to --post. The -f (or whatever) option creates the local csprocessor.cfg file for the spec so that further operations don't need a spec ID argument. Should fail if a local csprocessor.cfg already exists.
2. csprocessor build
Note: This will build the spec on the server, download it, unzip, publican build it, xdg-open it
3. Some local edits are made to the content spec
4. csprocessor updateremote
Note: updateremote performs a push, then a pull to refresh the local version. If the remote version can't be updated (because someone else edited it) then the updateremote fails

Comment 1 Joshua Wulf 2012-02-07 09:02:30 UTC

csprocessor.cfg has the following syntax:
-----------------------------------
SPECID=14
SPECNAME=Writing_with_Topics
-----------------------------------

Comment 2 Joshua Wulf 2012-02-23 14:41:22 UTC

csprocessor create <localfilename> is going to create a project.

What if I want to "check out an existing project"?

So I want to do something like:

csprocessor checkout <SpecID> [-s server.url]

The behaviour would be just like 

csprocessor create 

it would create the local directory, populate a csprocessor.cfg and pull the latest post-processed spec.

Comment 3 Lee Newson 2012-03-05 10:11:15 UTC

Added in 0.22.0.

The command is basically the same with the exception of the -s command which as with all the other commands is -H (or --host).