[
https://issues.apache.org/jira/browse/AMBARI-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877084#comment-13877084
]
Sumit Mohanty commented on AMBARI-4365:
---------------------------------------
Summary of changes:
* Remove DB/DAO support for action definitions
* Remove Create/Update/Delete support through APIs
* Add support for reading action definitions from XML files
* Wire-up executions of custom actions to the new way of getting action
definitions
> 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)
