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 #746: [WIP] Auto wrap YAML BOMs as catalog bundles
Date Mon, 03 Jul 2017 16:29:41 GMT
Github user ahgittin commented on the issue:

    https://github.com/apache/brooklyn-server/pull/746
  
    
    This now addresses templates in TypeRegistry -- simply using a "catalog_template" tag.
 There was no immediate need for "deployable" or "final" semantics so those have not been
added.
    
    This also addresses a newly-found issue to do with locations:  the location registry had
a hokey relationship with the old catalog; it's now a cleaner facade.  See comments in BasicLocationRegistry
for this.
    
    Finally I found a way to preserve the capability where the same BOM YAML is uploaded multiple
times:  if the bundle of the currently installed type was a wrapper, we now allow to replace
it if the plan itself is unchanged.  This removes the backwards compatibility issue introduced
around uploading a BOM multiple times and it disallowing because the containing bundle was
changed.
    
    The REST API however still points at the old catalog routines, so it won't yet show items
added through OSGi.  This is a showstopper of course because all BOMs will be added through
OSGi.  Fix for that coming soon.



---
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