David Pfingst created NIFI-14159:
------------------------------------
Summary: NIFI flexible Version Control
Key: NIFI-14159
URL: https://issues.apache.org/jira/browse/NIFI-14159
Project: Apache NiFi
Issue Type: Wish
Components: Flow Versioning
Affects Versions: 2.1.0
Reporter: David Pfingst
As a NiFi User / Admin I want to run Nifi with a complete deployment via GitLab
Pipeline so that it's not necessary to login into UI for bringing changes into
production environment. I want to use NiFi mostly headless with a single admin
user for service and other users only for monitoring purposes.
At the moment I'm using the NiFi REST API in a Pipeline script to achieve the
functions that aren't integrated into NiFi Version Control itself (deployment
of the new version) but there are restrictions that would be too complicated to
solve with the API. For an example the running state of the single processors
should be possible to get via version control. When I change the state of a
processor on my developement environment (local NiFi) this state should be set
on the production server as well when I deploy the new version.
My wishes for a flexible Version Control:
* Select per process group what should be versioned (checkbox for services,
running states, etc.)
* Version Control of Parameter providers (maybe passwords fillable with CI/CD
Variables from GitLab?)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
