<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Nifi toolkit command for GitLabFlowRegistry in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Nifi-toolkit-command-for-GitLabFlowRegistry/m-p/404942#M252399</link>
    <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/20288"&gt;@Shelton&lt;/a&gt;&amp;nbsp;for details!!&amp;nbsp; I will try Option 3 in our pipeline shell script.&amp;nbsp; &amp;nbsp;Will let you know if any further issues.&lt;/P&gt;</description>
    <pubDate>Thu, 27 Mar 2025 22:22:52 GMT</pubDate>
    <dc:creator>shiva239</dc:creator>
    <dc:date>2025-03-27T22:22:52Z</dc:date>
    <item>
      <title>Nifi toolkit command for GitLabFlowRegistry</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Nifi-toolkit-command-for-GitLabFlowRegistry/m-p/397087#M249690</link>
      <description>&lt;P&gt;I was able to setup&amp;nbsp;&lt;SPAN&gt;GitLabFlowRegistry in controller settings successfully (which is new feature in Nifi 2.0)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;From Nifi UI, I am able to import Nifi flow directly from Gitlab repository.&amp;nbsp; After modifications, I was able to successfully commit into Gitlab repo, from Nifi UI.&lt;BR /&gt;&lt;BR /&gt;Do we have any toolkit commands to perform these operations?&amp;nbsp; Currently we are using toolkit commands to deploy Nifi flow changes via CICD pipeline.&amp;nbsp; Can I achieve the same with new&amp;nbsp;GitLabFlowRegistry?&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Appreciate any help/pointers.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Nov 2024 22:23:32 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Nifi-toolkit-command-for-GitLabFlowRegistry/m-p/397087#M249690</guid>
      <dc:creator>shiva239</dc:creator>
      <dc:date>2024-11-06T22:23:32Z</dc:date>
    </item>
    <item>
      <title>Re: Nifi toolkit command for GitLabFlowRegistry</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Nifi-toolkit-command-for-GitLabFlowRegistry/m-p/404629#M252346</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/99414"&gt;@shiva239&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You've set up &lt;FONT color="#FF0000"&gt;GitLabFlowRegistry&lt;/FONT&gt; in NiFi 2.0's controller settings and&amp;nbsp;can import flows from GitLab and commit changes back through the UI your existing CI/CD pipeline uses NiFi toolkit commands.&lt;BR /&gt;As of NiFi 2.0, there aren't direct toolkit commands specifically designed for the new &lt;FONT color="#FF0000"&gt;GitLabFlowRegistry&lt;/FONT&gt; feature someone should correct me here. However, you have a few options to achieve what you need.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Option 1: Use the NiFi REST API&lt;/STRONG&gt;&lt;BR /&gt;The &lt;FONT color="#FF0000"&gt;GitLabFlowRegistry&lt;/FONT&gt; operations that you perform through the UI are backed by REST API endpoints. You can integrate these REST API calls into your CI/CD pipeline&lt;/P&gt;&lt;LI-SPOILER&gt;# Example REST API call to import/sync from Git repository&lt;BR /&gt;curl -X POST "&lt;A href="https://your-nifi-host:port/nifi-api/versions/process-groups/{processGroupId}/flow-registry-sync" target="_blank" rel="noopener"&gt;https://your-nifi-host:port/nifi-api/versions/process-groups/{processGroupId}/flow-registry-sync&lt;/A&gt;" \&lt;BR /&gt;-H "Content-Type: application/json" \&lt;BR /&gt;-d '{"registryId":"your-gitlab-registry-id","bucketId":"your-bucket-id","flowId":"your-flow-id","version":1}' \&lt;BR /&gt;--key your-key.key --cert your-cert.crt --cacert your-ca.crt&lt;/LI-SPOILER&gt;&lt;P&gt;&lt;STRONG&gt;Option 2: Hybrid Approach&lt;/STRONG&gt;&lt;BR /&gt;Use a combination of existing toolkit commands and REST API calls:&lt;/P&gt;&lt;OL class="lia-list-style-type-lower-alpha"&gt;&lt;LI&gt;Use toolkit commands for basic operations (deployment to a target NiFi instance)&lt;/LI&gt;&lt;LI&gt;Use REST API calls for &lt;FONT color="#FF0000"&gt;GitLabFlowRegistry-specific&lt;/FONT&gt; operations&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;STRONG&gt;Option 3: Create Custom Scripts&lt;/STRONG&gt;&lt;BR /&gt;You could create wrapper scripts that combine the toolkit functionality with the necessary REST API calls for &lt;FONT color="#FF0000"&gt;GitLabFlowRegistry&lt;/FONT&gt; operations:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-SPOILER&gt;&lt;P&gt;#!/bin/bash&lt;BR /&gt;# Custom script to sync from GitLabFlowRegistry and deploy&lt;/P&gt;&lt;P&gt;# First pull from Git registry via REST API&lt;BR /&gt;curl -X POST "&lt;A href="https://your-nifi-host:port/nifi-api/versions/process-groups/{processGroupId}/flow-registry-sync" target="_blank" rel="noopener"&gt;https://your-nifi-host:port/nifi-api/versions/process-groups/{processGroupId}/flow-registry-sync&lt;/A&gt;" \&lt;BR /&gt;-H "Content-Type: application/json" \&lt;BR /&gt;-d '{"registryId":"your-gitlab-registry-id","bucketId":"your-bucket-id","flowId":"your-flow-id","version":1}' \&lt;BR /&gt;--key your-key.key --cert your-cert.crt --cacert your-ca.crt&lt;/P&gt;&lt;P&gt;# Then use toolkit commands for additional operations as needed&lt;BR /&gt;./bin/cli.sh nifi pg-import ...&lt;/P&gt;&lt;/LI-SPOILER&gt;&lt;P class="whitespace-pre-wrap break-words"&gt;I recommend adopting Option 3 (custom scripts) for your CI/CD pipeline. This approach:&lt;/P&gt;&lt;OL class=""&gt;&lt;LI&gt;Takes advantage of the new &lt;FONT color="#FF0000"&gt;GitLabFlowRegistry&lt;/FONT&gt; feature&lt;/LI&gt;&lt;LI&gt;Maintains compatibility with your existing toolkit-based CI/CD pipeline&lt;/LI&gt;&lt;LI&gt;Provides flexibility to customize the process based on your specific requirements&lt;/LI&gt;&lt;/OL&gt;&lt;P class="whitespace-pre-wrap break-words"&gt;For implementing the REST API calls, consult the NiFi API documentation for the full set of endpoints related to the new &lt;FONT color="#FF0000"&gt;GitLabFlowRegistry&lt;/FONT&gt; functionality. The NiFi Admin Guide for version 2.0 should also have details on these new REST endpoints.&lt;BR /&gt;&lt;BR /&gt;Happy hadooping&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 23 Mar 2025 12:23:13 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Nifi-toolkit-command-for-GitLabFlowRegistry/m-p/404629#M252346</guid>
      <dc:creator>Shelton</dc:creator>
      <dc:date>2025-03-23T12:23:13Z</dc:date>
    </item>
    <item>
      <title>Re: Nifi toolkit command for GitLabFlowRegistry</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Nifi-toolkit-command-for-GitLabFlowRegistry/m-p/404942#M252399</link>
      <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/20288"&gt;@Shelton&lt;/a&gt;&amp;nbsp;for details!!&amp;nbsp; I will try Option 3 in our pipeline shell script.&amp;nbsp; &amp;nbsp;Will let you know if any further issues.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Mar 2025 22:22:52 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Nifi-toolkit-command-for-GitLabFlowRegistry/m-p/404942#M252399</guid>
      <dc:creator>shiva239</dc:creator>
      <dc:date>2025-03-27T22:22:52Z</dc:date>
    </item>
  </channel>
</rss>

