[
https://issues.apache.org/jira/browse/AMBARI-20616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeeta Ravindran updated AMBARI-20616:
----------------------------------------
Attachment: AMBARI-20616_updated.patch
Fixed checkstyle issue and incorporated review comments
> Provide an optional attribute for custom commands to allow using command name
> in operations window title
> --------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-20616
> URL: https://issues.apache.org/jira/browse/AMBARI-20616
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-sever
> Affects Versions: trunk
> Reporter: Sangeeta Ravindran
> Assignee: Sangeeta Ravindran
> Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-20616.patch, AMBARI-20616_updated.patch
>
>
> Some services in our stack have custom commands where the name is a
> combination of operation and component name.
> For e.g. <name>Remove_Logical_myservice_mycomponent</name>
> When the custom command is being executed, the operations window title is
> displayed as "Remove Logical myservice mycomponent mycomponent"
> It would be useful to provide an optional attribute e.g. useNameInOps for
> custom commands to allow using the command name itself as the title displayed
> in the operations window.
> <customCommand>
> <name>Remove_Logical_myservice_mycomponent</name>
> <useNameInOps>true</useNameInOps>
> <commandScript>
> <script>scripts/mycomponent.py</script>
> <scriptType>PYTHON</scriptType>
> <timeout>10800</timeout>
> </commandScript>
> </customCommand>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
