Bug 749414

Summary:	RFE: "strict" and "permissive" processing modes for Content Specs
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:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-04 10:13:42 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-27 00:41:46 UTC

Currently the title of existing topics in a content spec must match the topic title in skynet, or the content spec fails to push. 

Implement the ability to have a strict and permissive mode for processing:


In strict mode the title of existing topics in a content spec must match the title in skynet.

In permissive mode, the title doesn't have to match.

In permissive mode the postprocessed content spec will contain the topic titles as they are in skynet, not as they were specified in the preprocessed content spec.

Comment 1 Lee Newson 2011-10-28 02:21:05 UTC

Done. To use the mode via the client just use --permissive (-p for short).

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

*** Bug 750133 has been marked as a duplicate of this bug. ***