[NIFI-9452] Produce a c2 component manifest for NiFi at build time

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.16.0
• Component/s: C2
• Assignee: Bryan Bende
• Reporter: Bryan Bende
• Created: 07/Dec/21 16:12
• Updated: 04/Jan/22 18:12
• Resolved: 21/Dec/21 21:37

Description

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.

Issue Links

• is depended upon by: NIFI-9428 Implement C2 Protocol, Client, and Server
• is depended upon by: NIFI-9501 Add REST end-point to retrieve RuntimeManifest
• is depended upon by: NIFI-9502 Separate extension manifest model from nifi-registry
• links to: GitHub Pull Request #5612