Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 23 Jan 2014 18:38:38 +0000 (UTC)
From: "Sumit Mohanty (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12689930.1390269427683.2201.1390502318509@arcas>
In-Reply-To: <JIRA.12689930.1390269427683@arcas>
References: <JIRA.12689930.1390269427683@arcas>
Subject: [jira] [Resolved] (AMBARI-4365) Action definitions should be
 provided as declarative resources - read from XML files
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sumit Mohanty resolved AMBARI-4365.
-----------------------------------

    Resolution: Fixed

> Action definitions should be provided as declarative resources - read from XML files
> ------------------------------------------------------------------------------------
>
>                 Key: AMBARI-4365
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4365
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.5.0
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 1.5.0
>
>
> Currently, action definition are stored in database. This is not in-line with the declarative definition of stack and custom commands (as part of stack). The custom actions are essentially same as custom commands except they are defined at the level of clusters. So we should move the custom actions to XML formatted files that ambari-server can read when starting up. This means that when one needs to make any edit they will have to restart ambari-server. This requirement is OK as adding/modifying custom actions is not a frequently done operation.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)