Return-Path: 
 <dev-return-2287-apmail-brooklyn-dev-archive=brooklyn.apache.org@brooklyn.incubator.apache.org>
X-Original-To: apmail-brooklyn-dev-archive@minotaur.apache.org
Delivered-To: apmail-brooklyn-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id A230B1160B
	for <apmail-brooklyn-dev-archive@minotaur.apache.org>;
 Mon, 22 Sep 2014 11:13:24 +0000 (UTC)
Received: (qmail 93631 invoked by uid 500); 22 Sep 2014 11:13:24 -0000
Delivered-To: apmail-brooklyn-dev-archive@brooklyn.apache.org
Received: (qmail 93597 invoked by uid 500); 22 Sep 2014 11:13:24 -0000
Mailing-List: contact dev-help@brooklyn.incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@brooklyn.incubator.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@brooklyn.incubator.apache.org>
List-Post: <mailto:dev@brooklyn.incubator.apache.org>
List-Id: <dev.brooklyn.incubator.apache.org>
Reply-To: dev@brooklyn.incubator.apache.org
Delivered-To: mailing list dev@brooklyn.incubator.apache.org
Received: (qmail 93586 invoked by uid 99); 22 Sep 2014 11:13:23 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Sep 2014 11:13:23 +0000
X-ASF-Spam-Status: No, hits=-2000.8 required=5.0
	tests=ALL_TRUSTED,RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3)
    by apache.org (qpsmtpd/0.29) with SMTP; Mon, 22 Sep 2014 11:13:22 +0000
Received: (qmail 93518 invoked by uid 99); 22 Sep 2014 11:13:01 -0000
Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org)
 (140.211.11.114)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Sep 2014 11:13:01 +0000
Received: by tyr.zones.apache.org (Postfix, from userid 65534)
	id 61DBA94885D; Mon, 22 Sep 2014 11:13:01 +0000 (UTC)
From: ahgittin <git@git.apache.org>
To: dev@brooklyn.incubator.apache.org
Reply-To: dev@brooklyn.incubator.apache.org
References: <git-pr-175-incubator-brooklyn@git.apache.org>
In-Reply-To: <git-pr-175-incubator-brooklyn@git.apache.org>
Subject: [GitHub] incubator-brooklyn pull request: BROOKLYN-49: Catalogue
 persistenc...
Content-Type: text/plain
Message-Id: <20140922111301.61DBA94885D@tyr.zones.apache.org>
Date: Mon, 22 Sep 2014 11:13:01 +0000 (UTC)
X-Virus-Checked: Checked by ClamAV on apache.org

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