Bug 750784

Summary:	Pull a refreshed content spec
Product:	[Community] PressGang CCMS	Reporter:	Joshua Wulf <jwulf>
Component:	CSProcessor	Assignee:	Joshua Wulf <jwulf>
Status:	CLOSED WORKSFORME	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:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-04 08:58:39 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-11-02 11:35:19 UTC

This would be useful:

an option to 

skynet pull -c --post --refreshed

When this is executed, the post-processed content spec is retrieved by the processor, which then updates all the topic titles to the latest in the database.

This means that I can do all my title edits in the database, then pull an updated content spec.

That would be safer than pushing with --permissive.

Comment 1 Lee Newson 2011-11-04 03:10:34 UTC

Right now this can be accomplished by:

skynet pull -c --post <ID> -o tmp.txt
skynet push -ce --permissive tmp.txt

That will update the Content Spec on the server to the latest Topic Titles.

Comment 2 Joshua Wulf 2011-11-04 08:58:39 UTC

OK, so the best way to do it now is:

skynet pull -c --post <ID> -o tmp.txt
skynet push -ce tmp.txt
# Take a note of all the mismatching topic titles. If you want to update the content spec to the latest versions of the topic titles in the database
skynet push -ce --permissive tmp.txt
rm tmp.txt
# to see the updated content spec with the latest topic titles:
skynet pull -c --post <ID>