[jira] [Resolved] (WHIRR-370) Templating for configuration files

["Karel Vervaeke (Resolved) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WHIRR-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karel Vervaeke resolved WHIRR-370.
----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.9.0)
                   0.8.0

Committed to trunk
                
> Templating for configuration files
> ----------------------------------
>
>                 Key: WHIRR-370
>                 URL: https://issues.apache.org/jira/browse/WHIRR-370
>             Project: Whirr
>          Issue Type: Improvement
>          Components: core
>            Reporter: Tom White
>             Fix For: 0.8.0
>
>         Attachments: WHIRR-370.patch, WHIRR-370.patch, WHIRR-370.patch, WHIRR-370.patch, WHIRR-370.patch, WHIRR-370.patch
>
>
> Service configuration is currently done via the Whirr properties file by using a special per-service prefix (e.g. 'hadoop-common'). Using a templating approach (using e.g. Velocity) would make changing properties more familiar to users, and would make it easier for service implementors (since they wouldn't need to implement a generator class for each configuration file).
> It might even be possible to support the old syntax (so users can still configure everything from one file if they wished) by, e.g., appending all properties starting 'hadoop-common' to the core-site.xml template, etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira