Pierre Villard created NIFI-15673:
-------------------------------------
Summary: Add support for Author+Committer with git-based Flow
Registry Clients
Key: NIFI-15673
URL: https://issues.apache.org/jira/browse/NIFI-15673
Project: Apache NiFi
Issue Type: Improvement
Components: Flow Versioning
Reporter: Pierre Villard
Assignee: Pierre Villard
Right now, in NiFi, when using a git-based Flow Registry Client, all commits
are made with the identity that is configured for the authentication of the
registry client. It means that if many users are using the same NiFi UI, all
commits made by different users will be reported as being made with the same
user (likely the service account used in the registry client configuration).
This is not ideal when working with multiple users and trying to distinguish
who made the actual commits.
With the git-based implementations, it is possible to make a commit and specify
both an author and a committer.
This change is to use the identity of the NiFi User connected in the UI as the
author and use the identity configured in the registry client as the committer.
Important notes:
* the proposed implementation in GitHub is using reflection as a temporary
workaround until a submitted improvement is accepted/merged/released (see
[https://github.com/hub4j/github-api/pull/2200)]
* if the NiFi User does not resolve to an email address, the identity won't be
resolved on the git provider side and it will just show the author as an unkown
user with just the NiFi identity
* I didn't see an option to do that with Bitbucket Data Center
This has been tested with GitHub, GitLab, Azure DevOps and Bitbucket cloud.
A potential follow-up improvement would be to show this information in the UI
in the views where we list flow versions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
