exporting the canvas using the rest API
Hi, My team is developing a platform on Kubernetes that hosts NiFi instances for tenants. We are not giving tenants direct access to the running NiFi pods (docker containers). They will only have indirect access through NiFi’s rest API and also through one I am developing. After a tenant creates their canvas on our platform, I want to provide some means for them to export their canvas XML, basically to let them save it as another docker image. Unfortunately my own code is finding it impossible to use Kubernetes’s “Exec” service, I already lost a week trying that. Without that, I cannot easily export the canvas XML (flow.xml). The exec service would have let my own API run arbitrary commands on the pod (docker container), like cat /path/to/nifi/conf/flow.xml.gz for example. Is there any easy way for me to get the canvas (flow.xml) from NiFi using NiFi’s rest API? I am using NiFi 1.3. Michael Knapp The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
Re: UX issue w/ registry + NiFi
Sounds like a plan. When someone picks it up let me know and I will supply the users with test builds to get some user feedback to whoever picks it up. On Tue, Jun 19, 2018 at 1:15 PM Andy LoPresto wrote: > Hi Mike, > > I think that’s a great user request and something that requires > substantial discussion because it has been brought up before. I don’t think > it is worth delaying the release though. MiNiFi Java 0.5.0 needs NiFi to be > released first to gain the benefit of the new processors, etc. With our > always-improving release process, we can make another release soon if the > community feels there is a need for it. Thanks. > > > Andy LoPresto > alopre...@apache.org > *alopresto.apa...@gmail.com * > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > On Jun 19, 2018, at 10:12 AM, Mike Thomsen wrote: > > I'm working with a team that's doing some very visible work with the > registry, and one of the leads showed me that if someone even slightly > moves a UI element it registers as a change if the PG is versioned. That's > what they expect, but they'd really like the ability to lock down > components as they're working on them and then be able to lock down an > entire PG once they're done with it. I added a Jira ticket for it here: > > https://issues.apache.org/jira/browse/NIFI-5321 > > I know 1.7.0 is supposed to go up for a release vote soon, but I think this > ticket is a good UX reason to hold off a little. > > Thanks, > > Mike > > >
Re: UX issue w/ registry + NiFi
Hi Mike, I think that’s a great user request and something that requires substantial discussion because it has been brought up before. I don’t think it is worth delaying the release though. MiNiFi Java 0.5.0 needs NiFi to be released first to gain the benefit of the new processors, etc. With our always-improving release process, we can make another release soon if the community feels there is a need for it. Thanks. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Jun 19, 2018, at 10:12 AM, Mike Thomsen wrote: > > I'm working with a team that's doing some very visible work with the > registry, and one of the leads showed me that if someone even slightly > moves a UI element it registers as a change if the PG is versioned. That's > what they expect, but they'd really like the ability to lock down > components as they're working on them and then be able to lock down an > entire PG once they're done with it. I added a Jira ticket for it here: > > https://issues.apache.org/jira/browse/NIFI-5321 > > I know 1.7.0 is supposed to go up for a release vote soon, but I think this > ticket is a good UX reason to hold off a little. > > Thanks, > > Mike signature.asc Description: Message signed with OpenPGP using GPGMail
UX issue w/ registry + NiFi
I'm working with a team that's doing some very visible work with the registry, and one of the leads showed me that if someone even slightly moves a UI element it registers as a change if the PG is versioned. That's what they expect, but they'd really like the ability to lock down components as they're working on them and then be able to lock down an entire PG once they're done with it. I added a Jira ticket for it here: https://issues.apache.org/jira/browse/NIFI-5321 I know 1.7.0 is supposed to go up for a release vote soon, but I think this ticket is a good UX reason to hold off a little. Thanks, Mike
Setting values as System properties
Team, As part of NIFI-5133, I started doing some bit of research on Google Cloud PubSub service and it's support on proxy configuration and came to know that the service uses 'gRPC' so the proxy configuration is expected to be at the System properties level. I know this approach is not good and believe it has to be avoided but wanted to know the community's thoughts on this. Thanks, Sivaprasanna
Re: [RESULT][VOTE] Release Apache NiFi Registry 0.2.0
Thanks for RMing this Kevin. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Jun 18, 2018, at 23:45, Kevin Doran wrote: > > Apache NiFi Community, > > I am pleased to announce that the 0.2.0 release of Apache NiFi Registry > passes with: >9 +1 (binding) votes >3 +1 (non-binding) votes >0 0 votes >0 -1 votes > > Thanks to all who helped make this release possible! > > Here is the PMC vote thread: > https://lists.apache.org/thread.html/46d38f2cf9fda22d13d37f40dcb8557d123c499a36833060143efe62@ > > >
[RESULT][VOTE] Release Apache NiFi Registry 0.2.0
Apache NiFi Community, I am pleased to announce that the 0.2.0 release of Apache NiFi Registry passes with: 9 +1 (binding) votes 3 +1 (non-binding) votes 0 0 votes 0 -1 votes Thanks to all who helped make this release possible! Here is the PMC vote thread: https://lists.apache.org/thread.html/46d38f2cf9fda22d13d37f40dcb8557d123c499a36833060143efe62@
Re: [VOTE] Release Apache NiFi Registry 0.2.0
+1 from me as well, having verified the RC according to the steps in the release helper. On 6/18/18, 20:03, "James Wing" wrote: +1 (binding). Ran through the release helper, tested with a NiFi 1.7.0-SNAPSHOT build. Thanks, Kevin! On Fri, Jun 15, 2018 at 6:26 PM Kevin Doran wrote: > Hello, > > I am pleased to call this vote for the source release of Apache NiFi > Registry 0.2.0. > > The source zip, including signatures, digests, etc. can be found at: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-registry/nifi-registry-0.2.0/ > > The Git tag is nifi-registry-0.2.0-RC1 > The Git commit ID is 7966c52edd7a468fa30d32a333ef907e2b9e374c > > https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=7966c52edd7a468fa30d32a333ef907e2b9e374c > > Checksums of nifi-registry-0.2.0-source-release.zip: > SHA1: a3c2871b2e4dbadd537dec43ec6c28d1839f1706 > SHA256: ec824dcf39ce44cda8cb24c2049cc2920717161b0b6336fa4c3cfe759611637d > SHA512: > fe90234e9caa9e0bd7cc95f9a5f486e0f82a2b18e75d1df910b33c8d75fb965099d45f05dc094a41870f513b50219f8a6cdcf9d2fcd6b6f38e561c88d218 > > Release artifacts are signed with the following key: > Fingerprint = C09B A891 AED4 5B8C 2C23 1AFE 1FB6 6A91 F71B 6207 > Available at: > https://people.apache.org/keys/committer/kdoran.asc > https://pgp.mit.edu/pks/lookup?op=get=0x1FB66A91F71B6207 > > KEYS file available here: > https://dist.apache.org/repos/dist/dev/nifi/KEYS > > 46 issues were closed/resolved for this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920=12342369 > > Release note highlights can be found here: > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiRegistry0.2.0 > > The vote will be open for 72 hours. > Please download the release candidate and evaluate the necessary items > including checking hashes, signatures, build > from source, and test. Then please vote: > > [ ] +1 Release this package as nifi-registry-0.2.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because... > > >
