[ 
https://issues.apache.org/jira/browse/NIFIREG-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118986#comment-16118986
 ] 

ASF GitHub Bot commented on NIFIREG-8:
--------------------------------------

GitHub user kevdoran opened a pull request:

    https://github.com/apache/nifi-registry/pull/4

    NIFIREG-8: Registry Web API Stubs

    - Upgraded to latest version of Jersey
    - Upgraded to io.swagger annotations, latest version
    - Added resources for Bucket and Flow
    - Extended model to have the beginnings of concept for Bucket
    
    Next steps after this:
    - Add API endpoints for user/group/policy management
    - Possible rename some of the data model classes / packages to broaden the 
concept of "flow" data model to something more generic, as discussed with 
@bbende 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kevdoran/nifi-registry registry-web-api

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi-registry/pull/4.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4
    
----
commit 06369fee97309c3b1d0c29604a98ab6f829f281c
Author: Kevin Doran <kdoran.apa...@gmail.com>
Date:   2017-08-07T14:29:11Z

    WIP: NiFi Registry Web API endpoints

commit 0c23f1c1accec144a7ad62673167c2f700d20130
Author: Kevin Doran <kdoran.apa...@gmail.com>
Date:   2017-08-08T20:29:43Z

    WIP: NiFi Registry Web API endpoints

----


> Define Web REST API 
> --------------------
>
>                 Key: NIFIREG-8
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-8
>             Project: NiFi Registry
>          Issue Type: New Feature
>            Reporter: Kevin Doran
>
> Start to define a  REST Web API that will serve as the contract between 
> clients (e.g., NiFi) and the web service.



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

Reply via email to