[
https://issues.apache.org/jira/browse/NIFI-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597049#comment-16597049
]
ASF GitHub Bot commented on NIFI-5561:
--------------------------------------
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/2973
I created a flow which uses 3 `GenerateFlowFile` processors (named
_Component A_, _Component A_, and _Component A (B)_) to evaluate the new
filtering behavior. Each generates a flowfile with the content and _source_
attribute indicating the source (for the 2nd processor, the message & attribute
refer to _Component A (2)_). I exercised the
`SiteToSiteProvenanceReportingTask` with no accept/deny list, then only an
accept value, then both. The functionality worked as expected; explicit deny
overrode allow (see screenshot).
The template is [available
here](https://gist.github.com/alopresto/b78ec5da5482f4af7f88faf7eeefd3b7).
> Add component name filtering to S2S Provenance Reporting Task
> -------------------------------------------------------------
>
> Key: NIFI-5561
> URL: https://issues.apache.org/jira/browse/NIFI-5561
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
>
> I'd like to add component name as a way to filter events sent by the
> SiteToSite Provenance Reporting task so that, for example, all events
> generated by components containing "Prov" in the name are picked.
> This will be much easier to manage rather than component IDs as the ID of a
> component could change when a workflow is promoted from one environment to
> another in a CI/CD pipeline.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
