Re: [VOTE] Release Apache NiFi Registry 0.7.0

2020-07-17 Thread Marc Parisi
+1 binding Verified sigs and hashes Built and run on Linux LXC (Java 11) w/ Secured Apache NiFi built and run in the same container. All looked good Perused L and it looked good. Thanks, Marc On Fri, Jul 17, 2020 at 5:48 PM Peter Turcsanyi wrote: > +1 (non-binding) > > - verified signatures

Re: Failing to update custom processor properties names, displayNames, etc.

2020-07-17 Thread Andy LoPresto
Russell, Have you verified this is not a browser caching issue? They are pernicious and it sounds like this could be an example. If you’re sure it’s not, verify the API calls using your browser’s Developer Tools to see what properties are actually being returned by the server when inspecting

Failing to update custom processor properties names, displayNames, etc.

2020-07-17 Thread Russell Bateman
If I have changed a custom processor's PropertyDescriptor.nameand/or .displayName,including changes I have made to my /additionalDetails.html, /and I have: - removed that processor from my test flow or removed flow.xml.gz altogether - removed my NAR from /${NIFI_ROOT}///custom-lib/ and bounced

Re: [VOTE] Release Apache NiFi Registry 0.7.0

2020-07-17 Thread Peter Turcsanyi
+1 (non-binding) - verified signatures and checksums - built with Java 8 (empty local maven repo, OS: Ubuntu 18) - run NiFi Registry and connected to it from NiFi 1.11.4 (unsecure), performed some tests - download the convenience binary and tested a few things on it too Thanks, Peter On Fri,

Re: [VOTE] Release Apache NiFi Registry 0.7.0

2020-07-17 Thread Marton Szasz
+1 (non-binding) Followed the verification guide, migrated a test deployment using GitFlowPersistenceProvider from 0.6.0, then tested MiNiFi C++ C2 flow update using the new registry version. Thanks, Marton On Fri, 17 Jul 2020 at 18:36, Mark Payne wrote: > +1 (binding) > > Verified full build

Re: [VOTE] Release Apache NiFi Registry 0.7.0

2020-07-17 Thread Mark Payne
+1 (binding) Verified full build with contrib check, deployed and performed some tests, verifying that the FlowFiles concurrency and outbound policy was properly stored and retrieved. Thanks -Mark > On Jul 17, 2020, at 11:55 AM, Pierre Villard > wrote: > > +1 (binding) > > * went through

Re: [VOTE] Release Apache NiFi Registry 0.7.0

2020-07-17 Thread Pierre Villard
+1 (binding) * went through the usual release verification steps (signatures, build, contrib check, licenses) * deployed a local NR 0.7.0 instance with a single local NiFi 1.12.0-SNAPSHOT (non secure) Thanks Bryan for taking care of this! Le ven. 17 juil. 2020 à 17:46, Matt Burgess a écrit :

Re: [VOTE] Release Apache NiFi Registry 0.7.0

2020-07-17 Thread Andrew Lim
+1 (binding) -Ran full clean install on OS X (Catalina 10.15.2) -Tested secure NiFi Registry 0.7.0 with secure NiFi 1.11.4 -Tested basic flow, bucket and user functionality -Tested common versioned flow use cases -Reviewed documentation updates Drew > On Jul 15, 2020, at 11:31 AM, Bryan Bende

Re: [VOTE] Release Apache NiFi Registry 0.7.0

2020-07-17 Thread Matt Burgess
+1 (binding), verified hashes and commit ID, tested a few things on an unsecured instance. Thanks for RM'ing Bryan! On Wed, Jul 15, 2020 at 11:32 AM Bryan Bende wrote: > > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > Registry 0.7.0. > > The source zip,

Re: [VOTE] Release Apache NiFi Registry 0.7.0

2020-07-17 Thread Robert Fellows
+1 (non-binding) - Verified signature - Verified the hashes - Built and run with java 11 - Tested basic UI functionality and some REST endpoints. On Wed, Jul 15, 2020 at 11:32 AM Bryan Bende wrote: > Hello, > > I am pleased to be calling this vote for the source release of