[
https://issues.apache.org/jira/browse/MINIFICPP-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758358#comment-16758358
]
Mr TheSegfault edited comment on MINIFICPP-725 at 2/1/19 2:42 PM:
------------------------------------------------------------------
If for any reason you need the manifest
,[https://github.com/apache/nifi-minifi-cpp#deploying] will tell you how to use
the bootstrap script with a provided build identifier. The file build_output,
per the doc, will include that JSON manifest.
I think this may be closer to what you are seeking. The deploy script runs
this, but we can make this part of the normal build process.
[~srr] Given what is available above, would you prefer to see changes to
[https://github.com/apache/nifi-minifi-cpp/blob/master/PROCESSORS.md] so that
it becomes more clear where those processors originate?
Thanks!
was (Author: phrocker):
If for any reason you need the manifest
,[https://github.com/apache/nifi-minifi-cpp#deploying] will tell you how to use
the bootstrap script with a provided build identifier. The file build_output,
per the doc, will include that JSON manifest.
> Provide listing of enabled extensions to modules enabled during build
> -----------------------------------------------------------------------
>
> Key: MINIFICPP-725
> URL: https://issues.apache.org/jira/browse/MINIFICPP-725
> Project: NiFi MiNiFi C++
> Issue Type: Improvement
> Reporter: Aldrin Piri
> Priority: Major
>
> From the Apache NiFi Slack workspace
> (https://apachenifi.slack.com/archives/CDF1VC1UZ/p1548861784008700) a user
> expressed some confusion over what processors/extensions are enabled with the
> various features that are enabled. It would be helpful to have docs or some
> programmatic option during configuration that highlights what will be made
> available.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
