brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aled Sage (JIRA)" <j...@apache.org>
Subject [jira] [Created] (BROOKLYN-315) catalog .bom parsing should support `deprecated: true`
Date Tue, 12 Jul 2016 11:31:20 GMT
Aled Sage created BROOKLYN-315:
----------------------------------

             Summary: catalog .bom parsing should support `deprecated: true`
                 Key: BROOKLYN-315
                 URL: https://issues.apache.org/jira/browse/BROOKLYN-315
             Project: Brooklyn
          Issue Type: Improvement
    Affects Versions: 0.9.0
            Reporter: Aled Sage


I want to add deprecated items to the catalog via a yaml .bom. Under the covers, we have {{CatalogItem.setDeprecated()}}.
We can add support in the yaml parser to accept `deprecated: true`, and to set that on the
catalog item. 

See https://github.com/apache/brooklyn-server/pull/241 for an example of where we'd use this.
My specific use-case is the catalog items declared for use in Karaf. We have the deprecated
entity type {{org.apache.brooklyn.test.framework.SimpleShellCommandTest}}, which was renamed
to {{org.apache.brooklyn.test.framework.TestSshCommand}}. We should add the former to the
catalog so that existing blueprints work. But by marking it deprecated, we would be able to
hide it from UI drop-downs etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message