Bug 1011904
Summary: | RFE: Support multiple config files | ||
---|---|---|---|
Product: | [Community] PressGang CCMS | Reporter: | Ruediger Landmann <rlandman> |
Component: | CCMS-Core | Assignee: | Lee Newson <lnewson> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 1.1 | CC: | lnewson, mcaspers |
Target Milestone: | --- | ||
Target Release: | 1.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-10-17 23:49:26 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: | |||
Bug Depends On: | 979247 | ||
Bug Blocks: | 1012194, 1013825 |
Description
Ruediger Landmann
2013-09-25 11:14:13 UTC
Added in 1.2-SNAPSHOT build 201310111650 Content Spec: We've added two new metadata elements for content specs. The first is for adding the additional publican.cfg metadata, which is specified in the format "<NAME>-publican.cfg = [<CONTENT>]". eg publican.cfg = [git_branch: rhel-6-docs ] beta-publican.cfg = [condition: beta git_branch: rhel-6-docs] Then there is also the "Default publican.cfg = <NAME>" metadata, which is used to specify which file to use by default when building (to save having to specify it every time you want to build). (Note: The value can either be just <NAME> or <NAME>-publican.cfg) Building: For assembling we've added the "--publican-config <NAME>" option in the CLI to specify to build with something other than the "Default publican.cfg" file. eg "--publican-config beta" or "--publican-config beta-publican.cfg". For the additional publican.cfg files the following will still be set/overridden when building: "brand", "xml_lang" and "type". "docname", "product" and "version" will also be added to the additional configs if they aren't set by the user. I should also mention that all config files will be included in the build no matter what value is set for "Default publican.cfg". UI: In the UI we've also made these fields collapsible so that they don't hinder readability too much for extremely long configs. Tested adding new publican.cfg files to the specs, and tested collapsing them in the UI. csprocessor preview does not seem to respect the "Default publican.cfg" setting though. Fixed in 1.2-SNAPSHOT build 201310161156 The assemble (and therefore the preview) command wasn't using the Default publican.cfg value at all due to an issue where the command line arg was always being used. This has been updated so that the command line arg will override the content spec value, but only when specified. This still does not appear to work. With the settings JBoss-publican.cfg = [xml_lang: "en-US" brand: JBoss type: Book chunk_first: 1 formats: html,html-single,pdf show_remarks: 1] Default publican.cfg = JBoss and the command csprocessor preview 13968 -y the final output does not display any remarks. The above was tested with CSProcessor client version: 1.2-SNAPSHOT, Build 20131016-1033 Ignore the above comments - my version of csprocessor was not updated. csprocessor assemble now respects the Default publican.cfg directive. |