Bug 750133

Summary:	Add --db-canonical option for pushing content specs
Product:	[Community] PressGang CCMS	Reporter:	Joshua Wulf <jwulf>
Component:	CSProcessor	Assignee:	Lee Newson <lnewson>
Status:	CLOSED DUPLICATE	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-01 01:46:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	750131
Bug Blocks:

Description Joshua Wulf 2011-10-31 06:01:11 UTC

skynet push -c fails when the topic titles of existing topics in the Content Spec don't match the topic titles in the database.

If the user is presented with a list of the actual topic titles and the topic titles in the Content spec, (s)he may verify that in fact the topics specified are the ones (s)he wants, and they have simply been subjected to minor edits in skynet since the Content Spec was last constructed / updated.

In this case it would be useful for the user to be able to do this:

skynet push -c(n|e) --db-canonical filename.txt

When invoked with the --db-canonical option, when the processor encounters a mismatch between a specified topic title, rather than throwing an error the processor rewrites the title in the Content spec with the title from the database.

Comment 1 Lee Newson 2011-11-01 01:46:50 UTC

This does the exact same thing as the --permissive mode that was implemented last week and released with build 11.

*** This bug has been marked as a duplicate of bug 749414 ***