https://community.cloudera.com/t5/Support-Questions/Approval-review-workflow-audit-logging-for-Bitbucket-based/m-p/414525#M255449 <P>Hi all — we're migrating from NiFi Registry to the git-based Flow Registry Client, specifically the BitbucketFlowRegistryClient (NiFi 2.11.0), and validating the workflow.</P><P>From what we've seen so far, committing a flow version via the NiFi UI pushes directly to the configured Bitbucket branch, with no built-in approval step — any review has to happen externally via a Bitbucket PR after the fact.</P><P>Questions for the community:</P><P>Approval workflow: Is there any NiFi-native mechanism (now or planned) to gate a version commit behind a review/approval, or is external git-host PR review the intended pattern?<BR />Branching: For teams enforcing PR-based review on flow changes, do you commit to a feature branch by default and require manual PR creation, or is there tooling to automate opening the PR after a NiFi commit?<BR />Diffing: Any recommended pattern for diffing flow JSON in PRs on Bitbucket specifically? We saw Datavolo's Flow Diff GitHub Action for GitHub — is there an equivalent for Bitbucket, or does anyone have a working setup?<BR />Audit/logging: Beyond the git commit history (which only shows meaningful per-user attribution if using the "Application User" Commit Author Source), is there a recommended way to correlate NiFi's own Configuration History/Actions audit log with Bitbucket commit history, so we get a full picture of who changed what — both at the component level in NiFi and the version level in the repo?</P> Tue, 08 Sep 2026 13:18:35 GMT fy-test 2026-09-08T13:18:35Z https://community.cloudera.com/t5/Support-Questions/Approval-review-workflow-audit-logging-for-Bitbucket-based/m-p/414525#M255449 <P>Hi all — we're migrating from NiFi Registry to the git-based Flow Registry Client, specifically the BitbucketFlowRegistryClient (NiFi 2.11.0), and validating the workflow.</P><P>From what we've seen so far, committing a flow version via the NiFi UI pushes directly to the configured Bitbucket branch, with no built-in approval step — any review has to happen externally via a Bitbucket PR after the fact.</P><P>Questions for the community:</P><P>Approval workflow: Is there any NiFi-native mechanism (now or planned) to gate a version commit behind a review/approval, or is external git-host PR review the intended pattern?<BR />Branching: For teams enforcing PR-based review on flow changes, do you commit to a feature branch by default and require manual PR creation, or is there tooling to automate opening the PR after a NiFi commit?<BR />Diffing: Any recommended pattern for diffing flow JSON in PRs on Bitbucket specifically? We saw Datavolo's Flow Diff GitHub Action for GitHub — is there an equivalent for Bitbucket, or does anyone have a working setup?<BR />Audit/logging: Beyond the git commit history (which only shows meaningful per-user attribution if using the "Application User" Commit Author Source), is there a recommended way to correlate NiFi's own Configuration History/Actions audit log with Bitbucket commit history, so we get a full picture of who changed what — both at the component level in NiFi and the version level in the repo?</P> Tue, 08 Sep 2026 13:18:35 GMT https://community.cloudera.com/t5/Support-Questions/Approval-review-workflow-audit-logging-for-Bitbucket-based/m-p/414525#M255449 fy-test 2026-09-08T13:18:35Z