brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ahgittin <...@git.apache.org>
Subject [GitHub] brooklyn-server issue #338: Support nested catalog item definitions - testCa...
Date Mon, 06 Mar 2017 11:22:10 GMT
Github user ahgittin commented on the issue:

    https://github.com/apache/brooklyn-server/pull/338
  
    As for `catalogItemId`,  I think we should continue to populate and persist this.  It
is useful to know from whence something came, and for audit purposes this will become even
more important:  e.g. which version is it running.  I realize for persistence purposes we
can get the exact same class back using the search paths, but we want to be able to find instances
of `item:1.0` e.g. so we can upgrade them to `item:2.0`, and I think without the `catalogItemId`
field we won't be able to do that.  WDYT?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message