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 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  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 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.  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  Upon Successful Versioning, the Process Group should have the right check mark icon in Green Colour at the top left corner.  And, the following entry should be updated in the BitBucket UI  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).  Upon Commit Local Changes, the user will be prompted to add comments regarding the new version.    Upon successful save, the BitBucket UI should show updated Version details:  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  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. 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    ... View more

This article provides detailed steps about Encrypting and Decrypting files using the Pretty Good Privacy (PGP)  algorithm in NiFi Steps involve : Setting up GPG private key and Public key Creating NiFi flow  Setting up GPG private key and Public key Set up the GPG home directory  export GNUPGHOME=/tmp/gnupg​ Generate a private and public key  with a user ID gpg --full-generate-key gpg (GnuPG) 2.2.20; Copyright (C) 2020 Free Software Foundation, Inc. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Please select what kind of key you want: (1) RSA and RSA (default) (2) DSA and Elgamal (3) DSA (sign only) (4) RSA (sign only) (14) Existing key from card Your selection? 1 RSA keys may be between 1024 and 4096 bits long. What keysize do you want? (2048) 2048 Requested keysize is 2048 bits Please specify how long the key should be valid. 0 = key does not expire <n> = key expires in n days <n>w = key expires in n weeks <n>m = key expires in n months <n>y = key expires in n years Key is valid for? (0) 0 Key does not expire at all Is this correct? (y/N) y GnuPG needs to construct a user ID to identify your key. Real name: TestXYZ Email address: test@example.com Comment: You selected this USER-ID: "TestXYZ <test@example.com>" Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o There will be a prompt to enter a passphrase, which will be used later in the configuration There will be 4 files created under /tmp/gnupg Create a public and private keyring file in ASCII format  For the public keyring file, run the following command gpg --export --armor --output testexample.gpg.pub test@example.com For the Private keyring file, run the following command  gpg --export-secret-keys --armor --output testexample.gpg.asc test@example.com We would have two new files created under /tmp/gnupg Creating NiFi flow At this point, all set to create flow design using EncryptContentPGP and DecryptContentPGP, which use controller services StandardPGPPublicKeyService and StandardPGPPrivateKeyService  EncryptContentPGP configured with StandardPGPPublicKeyService DecryptContentPGP with StandardPGPPrivateKeyService  Note: In StandardPGPPrivateKeyService passphrase needs to be entered, which was set while running the gpg --full-generate-key command  Snapshot from working flow tested with .csv and .xlsx files      ... View more