Hello, The APIs are usable, but we really need NiFi 1.10.0 to be released first because in order to generate a NAR that can be version controlled in registry, the NAR must be built against nifi-api 1.10.0. If you are feeling ambitious you could build NiFi's master branch and build your NAR's against nifi-api 1.10.0-SNAPSHOT to try it out.
NiFi itself does not use these APIs yet, but hopefully one day there will be a nice UX for installing bundles from registry, and auto-installing required bundles when importing a flow. The NiFi CLI in 1.10.0 will have a bunch of commands to make working with these end-points easier. There is some basic information on how to use the end-points via curl [1]. -Bryan [1] https://nifi.apache.org/docs/nifi-registry-docs/html/user-guide.html#manage-bundles On Thu, Sep 12, 2019 at 2:46 PM Tim Dean <tim.d...@gmail.com> wrote: > > I am trying to understand the use of the NiFi registry’s bundles API > endpoints in version 0.4. We have numerous custom processors and controller > services and I am wondering if these new APIs will help manage versions for > these custom components. > > Are these APIs ready for production use? Are they documented anywhere other > than the Generated API docs? Does the rest of NiFi make use of these APIs yet? > > Thanks, > > -Tim
