You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/01/21 21:38:00 UTC

[jira] [Commented] (NIFI-9501) Add REST end-point to retrieve RuntimeManifest

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

ASF subversion and git services commented on NIFI-9501:
-------------------------------------------------------

Commit 6ef6e71d05d6f63a362b6195ce9bb9c652174293 in nifi's branch refs/heads/main from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6ef6e71 ]

NIFI-9501 Added REST end-point to retrieve a RuntimeManifest

- Switch ExtensionManifestParser implementation to use JAXB instead of Jackson XML
- Fix handling of older NARs that don't have newer fields in ExtensionManifest
- Add response merging for runtime-manifest REST end-point, remove commons-lang3 from c2 dependencies

This closes #5630

Signed-off-by: David Handermann <ex...@apache.org>


> Add REST end-point to retrieve RuntimeManifest
> ----------------------------------------------
>
>                 Key: NIFI-9501
>                 URL: https://issues.apache.org/jira/browse/NIFI-9501
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Bryan Bende
>            Assignee: Bryan Bende
>            Priority: Major
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> In NIFI-9452, the build will produce an artifact containing a C2 RuntimeManifest for the overall NiFi build.
> We should also support retrieving this manifest from a running NiFi instance, and should ensure that any NARs that are hot-loaded will also be included (i.e. don't create a static manifest during start up).



--
This message was sent by Atlassian Jira
(v8.20.1#820001)