You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Geoff Macartney (JIRA)" <ji...@apache.org> on 2019/03/16 18:39:00 UTC

[jira] [Created] (BROOKLYN-612) suggestion for improvement to docs for config

Geoff Macartney created BROOKLYN-612:
----------------------------------------

             Summary: suggestion for improvement to docs for config
                 Key: BROOKLYN-612
                 URL: https://issues.apache.org/jira/browse/BROOKLYN-612
             Project: Brooklyn
          Issue Type: Improvement
            Reporter: Geoff Macartney


During a discussion on the dev list one of our users suggested an improvement to the Brooklyn docs for config. List link is [here|https://lists.apache.org/thread.html/ca78e0b90343da2b0b96d8e759d7ccd2e3266e8ed09011ad29356a23@%3Cdev.brooklyn.apache.org%3E], but quoting the text here:
{quote}My problem is that even after reading and studying the examples, knowing that one can simply override an attribute value without brooklyn config, made it unclear for me what exactly the purpose or functionality of brooklyn.config was and how it differed from simple overriding of inherited values. Maybe the documentation could be improved so that brooklyn.config is given an explicit section rather than being an incidental part of several examples and a few comments provided. It would be helpful to understand what its scope is within a catalog item (where can it be declared and used) and what its intended scope is when composing an application where you set values.{quote}
 

I'm recording this as a good to-do for documentation improvement.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)