Greg Solovyev created NIFI-14086:
------------------------------------
Summary: Nifi toolkit pg-import command should allow specifying PG
name
Key: NIFI-14086
URL: https://issues.apache.org/jira/browse/NIFI-14086
Project: Apache NiFi
Issue Type: Improvement
Components: Tools and Build
Reporter: Greg Solovyev
Assignee: Greg Solovyev
Process groups templates in registry include name property, which translates
into process group name when importing a process group from a registry. This
makes it hard to have multiple instances of the same PG template within the
same NiFi instance. The example that I am dealing with is that a PG template
represents an implementation of a specific data connector (e.g., a connector
that reads events from a Windows Event Collection server or a Syslog server,
etc) and I need to deploy multiple copies of this connector to a single NiFi
instance where each copy reads from a separate server. I cannot do this without
accessing renaming process groups via NiFi UI or REST API, because
# once a single copy is deployed from the registry, all other copies will fail
to deploy due to name conflict.
# NiFi toolkit does not support renaming a process group
I have an implementation of this feature already in Anetac's NiFi fork
[https://github.com/apache/nifi/commit/a6d36a721e19aa44ff77514809b1ca001211848e,]
so this is just a matter of porting the change to main branch.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)