GitHub user ahgittin opened a pull request:

    https://github.com/apache/incubator-brooklyn/pull/617

    CLI commands for manipulating catalog, and cleaner catalog loading

    approx as discussed on mailing list, except annotations now also supported 
(easier to maintain compatibility, in tests)
    
    for review only at this point; i want to do more testing


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ahgittin/incubator-brooklyn catalog-cli

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-brooklyn/pull/617.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 #617
    
----
commit 20810ac9e275eadbf5c00c8b2ba07534841e56f5
Author: Alex Heneveld <[email protected]>
Date:   2015-04-23T06:46:32Z

    adjust cli start sequence so web/rest is avail always, with isUp check on 
rest api
    
    first step towards being able to interactively track the startup sequence 
and notify on errors

commit ddce439f17143e838291c8f60ab6b69610ed9249
Author: Alex Heneveld <[email protected]>
Date:   2015-04-23T10:52:53Z

    add ability to collect startup errors and check healthy through rest api
    
    changes defaults to be to continue on error, and extends (and optimizes) 
the BrooklynLauncherTest which checks this

commit e629602b41613f1068c9fa4b319e99dafc5eeeeb
Author: Alex Heneveld <[email protected]>
Date:   2015-04-23T15:31:30Z

    javascript checks up on start, shows caution
    
    popup now appears while server is starting, or if there are errors, and 
comes back if server changes to standby.
    changed to plug in *before* the routes are evaluated, so we don't load the 
wrong data.
    
    expands rest api to return several pieces of information to simplify gui 
checks.
    
    simplifies code in rest filters to block requests not compatible with 
server state, including checking for upness there.

commit 65d7ee3c15afda7c5ed4507889fb632f1e2d5c8f
Author: Alex Heneveld <[email protected]>
Date:   2015-04-27T11:53:09Z

    actually force catalog load by default, and report errors better
    
    and remove two incompatible items from the catalog, with comments in them - 
FollowTheSunPolicy and LoadBalancingPolicy

commit 7d0f1a0efeffd0e16bdca35ec73f0d7ebbd956ed
Author: Alex Heneveld <[email protected]>
Date:   2015-04-27T13:30:26Z

    show caution dialog if shutting down or if server is unresponsive
    
    and include shutting down message in rest api.
    tested that i can stop and restart the server and it nicely cycles through 
sequence of:
    "shutting down", "server unreachable", then "starting up", then restores 
page.

commit df36d992ee081f231f3a38b922f0a25d4476307b
Author: Alex Heneveld <[email protected]>
Date:   2015-04-27T13:38:05Z

    introduce CatalogInitialization to cleanly init catalog at the right times
    
    invoked during persistence cycles, and at startup, holding the new CLI 
catalog options.
    this does not yet properly initialize things for real-world use, and tests 
fixed in next commit.

commit 9f42c513743f531e4722d5132a6b43b3e0a89141
Author: Alex Heneveld <[email protected]>
Date:   2015-04-29T12:27:09Z

    yaml catalog supports scanning, experimental, and default
    
    this restores catalog scanning as the default, based on 
brooklyn/default.catalog.bom in the cli project;
    there are some limitations on what can be scanned, described in the doc.
    some of the tests configure other catalogs (with core's 
brooklyn/empty.catalog.bom used in many)

commit 9868d116b13e3b36b44edec47891f82a60d5436d
Author: Alex Heneveld <[email protected]>
Date:   2015-04-29T12:32:34Z

    item lister resources put in an appropriate subdir; other related tidies
    
    code was very ad hoc, but also polluting the root of the all jar; now 
resources at least are in a clean subdir

----


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

Reply via email to