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

Posted to issues@ambari.apache.org by "Hari Sekhon (JIRA)" <ji...@apache.org> on 2018/07/23 12:53:00 UTC

[jira] [Created] (AMBARI-24337) Ambari API - expose Ambari Config Revision Control

Hari Sekhon created AMBARI-24337:
------------------------------------

             Summary: Ambari API - expose Ambari Config Revision Control
                 Key: AMBARI-24337
                 URL: https://issues.apache.org/jira/browse/AMBARI-24337
             Project: Ambari
          Issue Type: Improvement
          Components: ambari-server
    Affects Versions: 2.5.2, 2.6.0
            Reporter: Hari Sekhon


Feature Request to expose Ambari Config Revision Control via Ambari API .

I had a look here but I don't think this is exactly what I want.

[https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/configuration.md]

I was thinking about writing a tool to fetch all Ambari Config Revisions as the online Ambari Revision Control is much too basic to be able to see config history across a team's changes over the course of say, a year.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)