Mailing-List: contact commits-help@ace.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ace.apache.org
Date: Sat, 30 Jan 2016 19:38:40 +0000 (UTC)
From: "J.W. Janssen (JIRA)" <jira@apache.org>
To: commits@ace.apache.org
Message-ID: <JIRA.12547186.1332247406000.257831.1454182720314@Atlassian.JIRA>
In-Reply-To: <JIRA.12547186.1332247406000@Atlassian.JIRA>
References: <JIRA.12547186.1332247406000@Atlassian.JIRA>
 <JIRA.12547186.1332247406758@arcas>
Subject: [jira] [Updated] (ACE-233) Allow pluggable update strategy/policy
 for the management agent
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

J.W. Janssen updated ACE-233:
-----------------------------
    Fix Version/s: next

> Allow pluggable update strategy/policy for the management agent
> ---------------------------------------------------------------
>
>                 Key: ACE-233
>                 URL: https://issues.apache.org/jira/browse/ACE-233
>             Project: ACE
>          Issue Type: Improvement
>          Components: Management Agent
>            Reporter: J.W. Janssen
>             Fix For: next
>
>
> The current management agent has two simple scheduled tasks that check for new versions and update to the latest version. While this is sufficient for many simple use-cases, it does not allow much room for customized update strategies/policies. For example, only update if explicitly approved by an user.
> All of this functionality resides inside the ace-deployment-task project, which exposes a minimal API to query/update a management agent. If the check/update tasks would be split off to another bundle, one could at least plug in other implementations for this functionality.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)