You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Nate Cole (JIRA)" <ji...@apache.org> on 2019/01/17 22:14:00 UTC
[jira] [Updated] (AMBARI-23444) Allow Custom Hooks on a Per-Role
Basis
[ https://issues.apache.org/jira/browse/AMBARI-23444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nate Cole updated AMBARI-23444:
-------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Allow Custom Hooks on a Per-Role Basis
> --------------------------------------
>
> Key: AMBARI-23444
> URL: https://issues.apache.org/jira/browse/AMBARI-23444
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent, ambari-server
> Affects Versions: trunk
> Reporter: Dmytro Grinenko
> Assignee: Dmytro Grinenko
> Priority: Critical
> Labels: pull-request-available
> Fix For: trunk
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Expand hooks with a service-specific hooks. In addition, we must use custom command parameters to help with this. For examples:
> {{before-KAFKA-INSTALL}}
> {{after-STORM-START}}
> {{after-KAFKA-RESTART}} <-- this is a custom command, not a "regular" command
>
> The more-specific hooks should execute tightly to the command script. For example:
> {{before-INSTALL}}
> {{before-KAFKA-INSTALL}}
> install script for Kafka
> {{after-KAFKA-INSTALL}}
> {{after-INSTALL}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)