[
https://issues.apache.org/jira/browse/NIFI-13644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881663#comment-17881663
]
endzeit commented on NIFI-13644:
--------------------------------
Thank you for taking a look at this @[~bbende].
Based on the [past discussion in
Slack](https://apachenifi.slack.com/archives/C0L9VCD47/p1723124879659449?thread_ts=1723035592.117289&cid=C0L9VCD47),
would it make sense to ensure compatibility between the Git-based
FlowRegistryClient implementations, e.g. using an abstract base class or
applying a contract test? That is, if we don't find a generic solution that
works for any git remote host provider.
Ideally users should be able to migrate Git host providers and keep their
history, e.g. move a Git project built from the "GitLabFlowRegistryProvider"
out of GitLab to GitHub and be able to consume it using the
"GitHubFlowRegistryProvider" (and vice versa).
> Implement a FlowRegistryClient that uses GitLab
> -----------------------------------------------
>
> Key: NIFI-13644
> URL: https://issues.apache.org/jira/browse/NIFI-13644
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: endzeit
> Assignee: Bryan Bende
> Priority: Major
>
> This ticket is to add an implementation of FlowRegistryClient that directly
> utilizes a GitLab repository.
> GitLab is used widely by corporations as an alternative to the popular GitHub.
> The implementation should work for both gitlab.com as well as self-hosted
> solutions.
> ----
> As part of this ticket, a more general approach using Git as baseline
> technology instead of introducing implementations specific to each Git remote
> hosting service vendor should be evaluated.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
