Thank you Andy. After any edits to the unzipped xml file, are there any particular options required by NiFi when the file is re-zipped with, say, gzip, so that NiFi does not reject it at start time? -Jim
On Wed, Jul 19, 2017 at 2:58 PM, Andy LoPresto <[email protected]> wrote: > Jim, > > It is compressed using GZIP, so you can simply uncompress the file to > view/modify the raw XML content of the flow definition. I wouldn’t > recommend editing the file directly in daily use, but I certainly do this > for debugging problematic user flows or when I was working on the sensitive > property encryption, for example. Here is an old mailing list item > regarding this [1]. > > [1] https://lists.apache.org/thread.html/b93ced98eff6a77dd0a2a2f0b5785e > f42a3b02de2cee5c17607a8c49@%3Cdev.nifi.apache.org%3E > > > Andy LoPresto > [email protected] > *[email protected] <[email protected]>* > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > On Jul 19, 2017, at 11:54 AM, James McMahon <[email protected]> wrote: > > Had an inquiry today whether flowfile.xml.gz can be modified indirectly > outside of the UI? It appears to be an encoded file of some sort so I am > guessing it is not possible, but wondered whether any tools had been > developed to do that? > > The use case would be to apply changes to a baseline flowfile.xml.gz in a > DevOps environment - for instance one might define environment-specific > settings in an Ansible script, so that a NiFi production instance could be > stood up rapidly, a different integration instance, a different dev > instance etc etc. > > Having worked with Pentaho for quite some time I have seen how readily > transform and job changes can be made at the xml file level. Has anyone > worked with tools that permit similar changes to flowfile.xml.gz outside > the UI? > > Thanks for any insights. -Jim > > >
