[
https://issues.apache.org/jira/browse/AMBARI-20739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015712#comment-16015712
]
Jonathan Hurley commented on AMBARI-20739:
------------------------------------------
I don't think that limiting the location is a bad idea. It might be overkill,
but I'm OK with it. Why don't we do something like this:
- Add a new configuration property to ambari.properties which indicates the
directory where alert scripts can live. Default it to
/var/lib/ambari-server/resources/scripts (or something like that).
- Any new script alert being created would need to exist in this location.
- As an admin, I can change this if I really want to something like
/net/share/ambari-server/scripts.
> Specify the script directly in alert target for script-based alert dispatchers
> ------------------------------------------------------------------------------
>
> Key: AMBARI-20739
> URL: https://issues.apache.org/jira/browse/AMBARI-20739
> Project: Ambari
> Issue Type: Task
> Components: alerts, ambari-web
> Affects Versions: 3.0.0
> Reporter: Yao Lei
> Assignee: Yao Lei
> Fix For: 3.0.0
>
>
> Although we can create the alert target of type ALERT_SCRIPT by web ui, we
> still need access to ambari.properties to add the new script and then
> restart ambari server to make this function take effect.It is better specify
> the script directly in alert target rather than in ambari.properties.In this
> way,we also don't need to restart ambari server.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
