[
https://issues.apache.org/jira/browse/AMBARI-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trevor McKay resolved AMBARI-1995.
----------------------------------
Resolution: Duplicate
This general fix for dynamic RoleCommandOrder objects has been subsumed into
2130.
> Allow RoleCommandOrder objects to be created dynamically with a StackId and
> AmbariMetaInfo as context
> -----------------------------------------------------------------------------------------------------
>
> Key: AMBARI-1995
> URL: https://issues.apache.org/jira/browse/AMBARI-1995
> Project: Ambari
> Issue Type: Improvement
> Affects Versions: 1.2.0
> Environment: Fedora/RHEL (but should be generally applicable)
> Reporter: Trevor McKay
> Assignee: Trevor McKay
> Attachments: RCO.patch
>
>
> Currently, the RoleCommandOrder object is created statically and defines
> fixed dependencies used for stage generation.
> It should be possible to create RoleCommandOrder objects with AmbariMetaInfo
> (injected by Guice) and a StackId argument to initialize(). This would allow
> the dependencies for stage planning to be generated relative to the
> particular stack being used.
> Generated RCOs can be cached against the StackId so they can be created once
> per StackId.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
