brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ahgittin <...@git.apache.org>
Subject [GitHub] incubator-brooklyn pull request: BROOKLYN-49: Catalogue persistenc...
Date Mon, 22 Sep 2014 11:13:01 GMT
Github user ahgittin commented on the pull request:

    https://github.com/apache/incubator-brooklyn/pull/175#issuecomment-56358860
  
    @aledsage suggested i look at the CLI/user side of house -- here's my thinking
    
    it seems to me that `--persistCatalog` could reasonably take the same options as `--persist`.
 this feels closer to what a user would want to do (e.g. prevent persistence = false would
be the same, but true would be expanded into force a rebind, force a clean start, or be smart
about it). the default could be `auto` (be smart) with an extra stipulation that if there
is no overall persistence, then `auto` here means no catalog persistence; ie you'd have to
supply a manual `clean` or `rebind` for `--persistCatalog` if you wanted the catalog persisted
but *not* entities etc (and I think it's fine if that is not supported)).  agree with the
behaviour that for `clean` or `auto` when there is no catalog yet, it would import `catalog.xml`
and attempt to persist it, warning if some items cannot be persisted.
    
    we could also have an `--importCatalog <file-or-url>` if we have to provide a way
for users to handle the case where some elements from `catalog.xml` cannot be persisted normally,
and they issue this each time on startup.  but no strong feelings if you think this is unnecessary.


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