[
https://issues.apache.org/jira/browse/AMBARI-8247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-8247:
---------------------------------
Attachment: example_reponse.json
Example response with {{kerberos_descriptor}} property included -
[^example_reponse.json]
Note the a lot of the {{kerberos_descriptor}} is related to configuration
properties embedded in the response as well. So maybe that relationship is a
reason to keep them together in the same resource rather than make the
{{kerberos_descriptor}} its own resource.
> Provide a way to get service-specific Kerberos descriptor via REST API
> ----------------------------------------------------------------------
>
> Key: AMBARI-8247
> URL: https://issues.apache.org/jira/browse/AMBARI-8247
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Labels: api, service, stack
> Fix For: 2.0.0
>
> Attachments: AMBARI-8247_01.patch, AMBARI-8247_02.patch,
> example_reponse.json
>
>
> Provide a way for a caller via the REST API to get information about a
> service's Kerberos descriptor. This information should probably be attached
> to a service resource response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
