Community Articles

Find and share helpful community-sourced technical articles.
Announcements
Now Live: Explore expert insights and technical deep dives on the new Cloudera Community BlogsRead the Announcement
Labels (1)
avatar
Master Collaborator

Apache NiFi 2.X or CFM Version 4.X now provide an ability to use Bitbucket as flow version control in place of NiFi Registry.

This new Registry Client is built with the name BitbucketFlowRegistryClient to connect to Bitbucket

Screenshot 2026-01-21 at 6.59.12 PM.png

To set up BitbucketFlowRegistryClient following information is required from the Bitbucket account as a prerequisite; if not present must be created 

  • Workspace Name
  • Repository Name
  • Authentication Type 
  • Default Branch
  • Repository Path

For this article Authentication Type is set to Access Token. This user needs to make sure the Access token is generated and kept handy from the Repository settings page in Bitbucket. Also, the user needs to make sure the Repository permissions are set up properly with Read and Write access on the Repository  

BitbucketFlowRegistryClient also needs StandardWebClientServiceProvider in the very first place as a Web Client Service to create an HTTP web client to connect to the Bitbucket API 

Screenshot 2026-01-21 at 7.55.06 PM.png

Once StandardWebClientServiceProvider is created and enabled from the Management Controller Services. From the Registry Client, add BitbucketFlowRegistryClient and configure.

StandardWebClientServiceProvider and other property values  as captured from Bitbucket as a prerequisite, and apply and enable the BitbucketFlowRegistryClient

Screenshot 2026-01-21 at 7.49.06 PM.png

After this, go and create a Process Group in NiFi if it has not been created before or if there are Process Groups created and a flow built inside, just right-click on the Process Group and click on Version with Start Version Control. 

Screenshot 2026-01-21 at 8.12.01 PM.png

This action will open the Save flow version page, where the user can provide the Flow Name, Flow Description, and Version Comments, and save it 

Screenshot 2026-01-21 at 8.14.42 PM.png

Upon Successful Versioning, the Process Group should have the right check mark icon in Green Colour at the top left corner. 

Screenshot 2026-01-21 at 8.16.36 PM.pngAnd, the following entry should be updated in the BitBucket UI 

Screenshot 2026-01-21 at 8.18.39 PM.png

Once the flow is published to BitBucket UI, and if there are further changes in the flow inside the Versioned process group, then the process group version icon will change from the right check to the gear icon, with Version menu items now showing (Commit/Show/Revert local changes /Stop version Control). 

Screenshot 2026-01-21 at 8.23.32 PM.png

Upon Commit Local Changes, the user will be prompted to add comments regarding the new version.   

Screenshot 2026-01-21 at 8.24.35 PM.png

Upon successful save, the BitBucket UI should show updated Version details: 

Screenshot 2026-01-21 at 8.26.18 PM.png

At this point, the flows can be deployed into NiFi from BitBucket through version control. To do this use click on the Import from Registry icon in the NiFi UI 

Screenshot 2026-01-21 at 8.29.35 PM.png

Import from the Registry window should show all the versions of the flow that were published in earlier steps into BitBucket. Select the desired version and import the from Into NiFi from BitBucket.

Screenshot 2026-01-21 at 8.30.13 PM.png

Note: Apache NiFi 2.7.2 version is used to prepare the snapshots, few properties may vary between Apache NiFi 2.X vs CFM 4.X, but all the required ones are there. 

Thank you 

 

71 Views
0 Kudos
Version history
Last update:
‎01-22-2026 07:22 AM
Updated by:
Contributors