nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (NIFIREG-8) Define Web REST API
Date Tue, 08 Aug 2017 20:39:00 GMT


ASF GitHub Bot commented on NIFIREG-8:

GitHub user kevdoran opened a pull request:

    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 registry-web-api

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

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 <>
Date:   2017-08-07T14:29:11Z

    WIP: NiFi Registry Web API endpoints

commit 0c23f1c1accec144a7ad62673167c2f700d20130
Author: Kevin Doran <>
Date:   2017-08-08T20:29:43Z

    WIP: NiFi Registry Web API endpoints


> Define Web REST API 
> --------------------
>                 Key: NIFIREG-8
>                 URL:
>             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

View raw message