Bug 809319

Summary:	RFE: Warn/Act on RH-Internal-Only topic inclusion
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.24.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-06-07 01:30:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Joshua Wulf 2012-04-03 05:36:53 UTC

I've created an "RH-Internal-Only" tag for topics. 

Topics containing Red Hat-confidential information such as internal server urls and so forth, should be tagged with this tag, and the RFE is that the system should warn when this content is included in a book / other output and possibly disallow certain combinations of operations based on this tag.

For example: we could even check the publican.cfg content in the content spec to enforce that no content spec can be tagged against the public git tag *and* contain RH-Internal-Only tagged topics.

This will prevent private information from being published.

Comment 1 Lee Newson 2012-05-18 14:02:19 UTC

Added in 0.24.0

If a topic is tagged with the Internal-Only tag a message will be displayed when pushing, validating or building. The message is "The topic is an internal-only topic and contains sensitive information. Ensure you are not publishing this publicly."

Comment 2 Lee Newson 2012-05-18 14:03:40 UTC

As for the publican.cfg it's impossible with out a list to determine if the git repo is a public one. Also doing this would then bind the processor to those repo, which shouldn't happen.

Comment 3 Lee Newson 2013-06-07 01:30:36 UTC

Closing and setting as current release as no QA was performed by the original reporter. If there is still an issue with this bug still than please re-open it.