[
https://issues.apache.org/jira/browse/AMBARI-18210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-18210:
---------------------------------
Fix Version/s: (was: 2.5.0)
> Add-on service management-pack should be able to contribute custom repo
> locations
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-18210
> URL: https://issues.apache.org/jira/browse/AMBARI-18210
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Balázs Bence Sári
> Assignee: Balázs Bence Sári
> Priority: Blocker
>
> The approach for custom-services to specify their own repo location will be
> to provide a {{/repos/repoinfo.xml}} inside the stack-version they will be
> in. This repo file will be loaded by Ambari during startup into the
> {{/api/v1/stacks/HDP/versions/2.4/repository_versions}} repos. *Service repo
> files have a restriction that their (repo-name, base-url) locations should be
> unique and not conflict*. When conflicts do occur, they will not be loaded
> into the stacks model.
> Now the management-pack will provide such repos/ folder in
> {{mpacks/custom-services/8.0.0/repos}} which will be linked into the stacks/
> folder.
> {{ambari/ambari-server/src/main/resources/stacks/HDP/2.3/services/SERVICE_NAME/repos
> -> mpacks/custom-services/8.0.0/repos}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
