[
https://issues.apache.org/jira/browse/METRON-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830032#comment-15830032
]
ASF GitHub Bot commented on METRON-503:
---------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/incubator-metron/pull/316
I would very much prefer to not wait. There are other endpoints outside of
configuration management that we need, a REST API isn't limited to just that.
If we feel we should remove the auditing functions I am happy to do that. With
the auditing functions removed, there will not be major changes needed once
configuration management is moved to Ambari.
@ottobackwards, I don't understand what you mean by this:
"Also, the point that this may be better managed from within ambari as a
view may need consideration."
Can you expand on that?
> Metron REST API
> ---------------
>
> Key: METRON-503
> URL: https://issues.apache.org/jira/browse/METRON-503
> Project: Metron
> Issue Type: New Feature
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
> Attachments: Metron REST API.docx
>
>
> As discussed on the dev list ([DISCUSS] Metron REST API Requirements), this
> Jira includes adding a REST API to Metron.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
