[
https://issues.apache.org/jira/browse/NIFI-9452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17468727#comment-17468727
]
ASF subversion and git services commented on NIFI-9452:
-------------------------------------------------------
Commit 0f02dac3fa57885ed47957211f1abd36af69f7ed in nifi's branch
refs/heads/NIFI-9428 from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0f02dac ]
NIFI-9452 Generate a RuntimeManifest for NiFi at build time
- Write additional fields to extnesion-manifest.xml for processors
- Update C2 model classes to support new fields for processors, properties, and
scheduling
- Create converter between NiFi model and C2 model
- Create generator and execute during the build
Add profile to nifi-assembly that skips the binary assembly, update github
workflow to enable this profile instead of excluding nifi-assembly
Add additional documentation on new fields in processor definition and
reporting task definition
Set charset to UTF-8 on the OutputStreamWriter
Signed-off-by: Matthew Burgess <[email protected]>
This closes #5612
> Produce a c2 component manifest for NiFi at build time
> ------------------------------------------------------
>
> Key: NIFI-9452
> URL: https://issues.apache.org/jira/browse/NIFI-9452
> Project: Apache NiFi
> Issue Type: Improvement
> Components: C2
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Major
> Fix For: 1.16.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Once NIFI-9430 is completed, we will have an initial c2-protocol-api module
> that defines an agent manifest, which contains a component manifest.
> We also have all of the extension-manifest.xml definitions that are in each
> NAR, and are now bundled up as part of the assembly.
> We should take all of the extension-manifest.xml definitions and use them as
> input to produce a single c2 runtime manifest for the nifi build.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
