GitHub user ahgittin opened a pull request:
https://github.com/apache/brooklyn-server/pull/645
[WIP] persist OSGi bundles
This works to persist bundles and is ready for review. However it has
conflicts and needs to be reconciled with #338 -- both coming soon.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ahgittin/brooklyn-server persist-osgi-bundles
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/645.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #645
----
commit dfd12ee599ce7bd9c88847693be8ae5c344968d3
Author: Alex Heneveld <[email protected]>
Date: 2017-04-19T18:11:56Z
bulk of structural additions to support persisting osgi bundles
not yet actually writing or reading bundle zip data, nor installing them,
but saving metadata, and clear now where to add the binary zip data
commit 38dde8b6e6b029130679e543f2d9d382720d3dc9
Author: Alex Heneveld <[email protected]>
Date: 2017-04-20T16:01:01Z
osgi bundle persistence code written ... but not yet tested.
need to write unit test for persistence, and do manual test against S3 or
similar.
then the fun stuff, CLI push and upgrade workflow, bundles used in search
path instead of catalog item id, bundles managed in REST/UI
commit 41fd62fac073d7ee96a35fceb4cbb8f0f5abb218
Author: Alex Heneveld <[email protected]>
Date: 2017-04-21T10:52:02Z
done the basics, bundle persistence working and with a test
note `PersistenceObjectStore` for accessing blob store impls have been
changed to handle byte streams better
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
