brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ahgittin <>
Subject [GitHub] incubator-brooklyn pull request: Versioning catalog items
Date Wed, 30 Jul 2014 13:42:05 GMT
Github user ahgittin commented on the pull request:
    I think we need some way of finding a default.  Without this existing YAML blueprints
break, the simple "add app" from a catalog breaks, and users have to know blueprint versions
to do anything.
    Based on external discussions, my suggestions are to support both versionless items and
latest-semver-release semantics.  Specifically:
    * Where an entity is registered/available without version information (explicitly added
to catalog without version or picked up from java classes) we:
      * Use it when the user has not suggested version
      * Allow it to be replaced if an updated item is added with the same name/id and no version
      * Where a catalog item is added without version information we refer to it as an "alias"
and recommend that it point via YAML to a versioned item
    * Where an entity is registered/available with version information:
      * If the user specifies a version, we must match it exactly (and in time, we may support
a version range from the user)
      * If the user does not specify a version, we look for an "alias" with that ID (ie no
version information), if there is none we look for the most recent release version (as per
semver), and if there is still none we look for a java class with that name
      * We require an extra "force" parameter if someone wants to replace it (with the same
version), or if they want to delete it when it is in use

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 or file a JIRA ticket
with INFRA.

View raw message