From commits-return-84334-archive-asf-public=cust-asf.ponee.io@cloudstack.apache.org  Mon Jan  7 16:38:08 2019
Return-Path: <commits-return-84334-archive-asf-public=cust-asf.ponee.io@cloudstack.apache.org>
X-Original-To: archive-asf-public@cust-asf.ponee.io
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by mx-eu-01.ponee.io (Postfix) with SMTP id 6032B180647
	for <archive-asf-public@cust-asf.ponee.io>; Mon,  7 Jan 2019 16:38:08 +0100 (CET)
Received: (qmail 98724 invoked by uid 500); 7 Jan 2019 15:38:06 -0000
Mailing-List: contact commits-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@cloudstack.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@cloudstack.apache.org>
List-Post: <mailto:commits@cloudstack.apache.org>
List-Id: <commits.cloudstack.apache.org>
Reply-To: dev@cloudstack.apache.org
Delivered-To: mailing list commits@cloudstack.apache.org
Received: (qmail 98715 invoked by uid 99); 7 Jan 2019 15:38:06 -0000
Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jan 2019 15:38:06 +0000
From: GitBox <git@apache.org>
To: commits@cloudstack.apache.org
Subject: [GitHub] nathanejohnson opened a new pull request #3122: The
 snapshot.backup.rightafter configuration variable was removed by:
Message-ID: <154687548627.1258.5818189518199807903.gitbox@gitbox.apache.org>
Date: Mon, 07 Jan 2019 15:38:06 -0000
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

nathanejohnson opened a new pull request #3122: The snapshot.backup.rightafter configuration variable was removed by:
URL: https://github.com/apache/cloudstack/pull/3122
 
 
   ## Description
   
   SHA: 6bb0ca2f854
   
   This adds it back, though named snapshot.backup.to.secondary now instead.
   
   This global parameter, once set, will allow you to prevent automatic backups of
        snapshots to secondary storage, unless they're actually needed.
   
   Fixes #3096
   
   
   <!--- Describe your changes in detail -->
   
   <!-- For new features, provide link to FS, dev ML discussion etc. -->
   <!-- In case of bug fix, the expected and actual behaviours, steps to reproduce. -->
   
   <!-- When "Fixes: #<id>" is specified, the issue/PR will automatically be closed when this PR gets merged -->
   <!-- For addressing multiple issues/PRs, use multiple "Fixes: #<id>" -->
   <!-- Fixes: # -->
   
   ## Types of changes
   <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
   - [ ] Breaking change (fix or feature that would cause existing functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [x] Bug fix (non-breaking change which fixes an issue)
   - [ ] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   
   ## How Has This Been Tested?
   tested this in our 4.11 lab environment
   
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services