Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
From: jburwell <git@git.apache.org>
To: dev@cloudstack.apache.org
Reply-To: dev@cloudstack.apache.org
References: <git-pr-1773-cloudstack@git.apache.org>
In-Reply-To: <git-pr-1773-cloudstack@git.apache.org>
Subject: [GitHub] cloudstack issue #1773: CLOUDSTACK-9607: Preventing template deletion when t...
Content-Type: text/plain
Message-Id: <20170221135524.188A1DFF0F@git1-us-west.apache.org>
Date: Tue, 21 Feb 2017 13:55:24 +0000 (UTC)
archived-at: Tue, 21 Feb 2017 13:55:26 -0000

Github user jburwell commented on the issue:

    https://github.com/apache/cloudstack/pull/1773
  
    @priyankparihar I agree with @ustcweizhou regarding the default value of `forced` in terms of backwards compatibility.
    
    Also, why we permit deletion of a template when it is associated with one or more active volumes?  It seems like we are giving the user the means to corrupt their system.


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