<?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: Can we create a NiFi workflow and operate using CLI instead of GUI? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Can-we-create-a-NiFi-workflow-and-operate-using-CLI-instead/m-p/96550#M10064</link>
    <description>&lt;P&gt;Its probably possible (because Nifi is REST API based) but in general, the recommendation is to create a template from existing flow ahead of time and importing into Nifi on your desired cluster (that would be easier to automate than automating the building of the whole flow)&lt;/P&gt;</description>
    <pubDate>Thu, 05 Nov 2015 11:25:41 GMT</pubDate>
    <dc:creator>abajwa</dc:creator>
    <dc:date>2015-11-05T11:25:41Z</dc:date>
    <item>
      <title>Can we create a NiFi workflow and operate using CLI instead of GUI?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Can-we-create-a-NiFi-workflow-and-operate-using-CLI-instead/m-p/96549#M10063</link>
      <description>&lt;P&gt;One of our prospects is looking at NiFi, they cant have GUI operated tools as they need everything to be scripted for ease of operations, can we create and manage NiFi flows with CLI without the need for GUI?&lt;/P&gt;</description>
      <pubDate>Tue, 21 Apr 2026 12:34:36 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Can-we-create-a-NiFi-workflow-and-operate-using-CLI-instead/m-p/96549#M10063</guid>
      <dc:creator>nshawa</dc:creator>
      <dc:date>2026-04-21T12:34:36Z</dc:date>
    </item>
    <item>
      <title>Re: Can we create a NiFi workflow and operate using CLI instead of GUI?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Can-we-create-a-NiFi-workflow-and-operate-using-CLI-instead/m-p/96550#M10064</link>
      <description>&lt;P&gt;Its probably possible (because Nifi is REST API based) but in general, the recommendation is to create a template from existing flow ahead of time and importing into Nifi on your desired cluster (that would be easier to automate than automating the building of the whole flow)&lt;/P&gt;</description>
      <pubDate>Thu, 05 Nov 2015 11:25:41 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Can-we-create-a-NiFi-workflow-and-operate-using-CLI-instead/m-p/96550#M10064</guid>
      <dc:creator>abajwa</dc:creator>
      <dc:date>2015-11-05T11:25:41Z</dc:date>
    </item>
    <item>
      <title>Re: Can we create a NiFi workflow and operate using CLI instead of GUI?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Can-we-create-a-NiFi-workflow-and-operate-using-CLI-instead/m-p/96551#M10065</link>
      <description>&lt;P&gt;There's a difference between modifying your flow in-flight, realtime (possible, but requires some effort from the developer), and automating deployment for operations. Templates provide a middle ground, whereas one doesn't need to wire everything programmatically, but rather piece together large chunks of the flow only.&lt;/P&gt;&lt;P&gt;Today, you can simply set up the flow the way you need and bundle the complete &lt;STRONG&gt;conf/flow.xml.gz &lt;/STRONG&gt;file together with a newly deployed instance. This way you deploy NiFi with a complete flow already deployed.&lt;/P&gt;&lt;P&gt;The operations side will see many improvements going forward, but today these are the options.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Nov 2015 21:05:48 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Can-we-create-a-NiFi-workflow-and-operate-using-CLI-instead/m-p/96551#M10065</guid>
      <dc:creator>andrewg</dc:creator>
      <dc:date>2015-11-05T21:05:48Z</dc:date>
    </item>
  </channel>
</rss>

