You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2015/03/20 23:02:38 UTC
[jira] [Updated] (AMBARI-10164) Provide /artifacts/theme endpoint
for each stack-version service
[ https://issues.apache.org/jira/browse/AMBARI-10164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Srimanth Gunturi updated AMBARI-10164:
--------------------------------------
Attachment: AMBARI-10164.patch
Committed patch to trunk after fixing RAT check failure.
> Provide /artifacts/theme endpoint for each stack-version service
> ----------------------------------------------------------------
>
> Key: AMBARI-10164
> URL: https://issues.apache.org/jira/browse/AMBARI-10164
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Myroslav Papirkovskyy
> Assignee: Myroslav Papirkovskyy
> Fix For: 2.1.0
>
> Attachments: AMBARI-10164.patch
>
>
> In the stack definition we will be providing theme for each service. This needs to be provided at the /api/v1/stacks/HDP/versions/2.2/services/HDFS/artifacts/theme endpoint. Internally the theme.json should be extensible by stack-version just like configs.
> Similar to the way configs are overridden in the stack, config-layout should have the possibility of inheritance as well as ability to override specific portions of the layout, or complete replacement of layout.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)