You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by "J.W. Janssen (JIRA)" <ji...@apache.org> on 2016/01/30 20:38:40 UTC

[jira] [Updated] (ACE-233) Allow pluggable update strategy/policy for the management agent

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