You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2017/11/10 17:16:00 UTC

[jira] [Created] (AMBARI-22418) Make Ambari configuration API consistent with existing API.

Robert Levas created AMBARI-22418:
-------------------------------------

             Summary: Make Ambari configuration API consistent with existing API.
                 Key: AMBARI-22418
                 URL: https://issues.apache.org/jira/browse/AMBARI-22418
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 3.0.0
            Reporter: Robert Levas
            Assignee: Robert Levas
             Fix For: 3.0.0


Make Ambari configuration API consistent with existing API. 

The current API entry point (as of AMBARI-21307) is {{/api/v1/ambariconfigs}}. This should be more inline with the existing entry point for Ambari server related data...  {{/api/v1/services/AMBARI/components/AMBARI_SERVER}}.  

The new API entry point for Ambari server related configuration data should be {{/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations}}.






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)