I'm setting up nifi 2.3.0 with GitHubRegistryClient to by-pass the nifi registry component. When configuring GitHubRegistryClient:
- I used the bitbucket repo https clone url
- I created PAT(Personal Access Token)
- I verified that I can git clone the repo in the container where nifi is also running
However, when I try to import flows, I got this error:
Unable to get branches for registry with ID 5xxxxx-xxxxx-xxxxb: Invalid request from host ##.##.##.#: Note that Bitbucket does not support Git's legacy HTTP transport protocol.
It seems that bitbucket is complaining about nifi git client is trying to connect over http? However the url is pointing to https and the PAT is for https as well. (https://confluence.atlassian.com/bitbucketserver/http-access-tokens-939515499.html) I tried to set nifi.security.ssl.protocol=TLSv1.3 It does not fix the issue.
Update: I'm using GitHubRegistryClient to connect to BitBucket. Is that recommended?
I corrected the GitHub URL with the bitbucket rest API url: https://bitbucket.company.com/rest/api/1.0/projects THen specify the repo owner as projects and give the repo name
Now I don't see the previous error but another error: owner/repo cannot be found.
I'm wondering if this is related to the rest API convention is different from github and bitbucket
The bitbucket url template is https://bitbucket.company.com/rest/api/1.0/projects/<project_name>/repos/<repo_name>
Do I have to go back to nifi registry as a middle man solution?
