brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aledsage <...@git.apache.org>
Subject [GitHub] brooklyn-docs pull request #228: add docs on upgrades esp new blueprint bund...
Date Tue, 14 Nov 2017 12:29:10 GMT
Github user aledsage commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/228#discussion_r150816562
  
    --- Diff: guide/ops/upgrades/_blueprints.md ---
    @@ -0,0 +1,50 @@
    +
    +## Upgrading Blueprints and Bundles
    +
    +You can install and deploy new versions of blueprints at any time.
    +Brooklyn tracks multiple versions of the blueprints you install, as can be seen in the
catalog.
    +
    +
    +### Defining and Forcing Upgrade Paths
    +
    +Bundles can declare what bundles and types they can upgrade,
    +and they can also force the removal of installed bundles and types on startup/rebind.
    +Forcing can be useful when upgrading Brooklyn to replace any installed bundle
    +not compatible with the newer version of Brooklyn.
    +
    +To add these definitions, use the following headers in the bundle's OSGi `META-INF/MANIFEST.MF`:
    +
    +* `Brooklyn-Catalog-Force-Remove-Bundles`
    +* `Brooklyn-Catalog-Force-Remove-Legacy-Items`
    +* `Brooklyn-Catalog-Upgrade-For-Bundles`
    +* `Brooklyn-Catalog-Upgrade-For-Types`
    +
    +The most common patterns are to indicate that a bundle can replace all previous versions
of itself
    +and all types thereing with types in the current bundle of the same name, using:
    --- End diff --
    
    typo: `therin`


---

Mime
View raw message