Thanks for kicking off the discussion Joe! Of the many items that could be included in the next release, securing the default configuration as described in NIFI-8220 <https://issues.apache.org/jira/browse/NIFI-8220> would be great to have completed. Most of the elements are in place, and the current Pull Request for NIFI-8516 <https://github.com/apache/nifi/pull/5068> is under review. If there are any other achievable items that should be included as part of a secure default installation for NiFi, it would be helpful to add sub-tasks to NIFI-8220. The current scope is limited to a standalone installation, so issues regarding clustered deployments can be handled separately. If others are interested in evaluating the proposed new default configuration that requires HTTPS and leverages a generated username and password, feel free to provide feedback on NIFI-8516.
Regards, David Handermann On Thu, May 27, 2021 at 6:51 PM Otto Fowler <ottobackwa...@gmail.com> wrote: > I think NIFI-8625 and NIFI-8461 need to be understood and addressed. > > > > On May 27, 2021, at 13:29, Joe Witt <joe.w...@gmail.com> wrote: > > > > Team, > > > > There has been a tremendous amount of work already on the 1.14 line as > shown: > > > > https://issues.apache.org/jira/projects/NIFI/versions/12349644 > > > > These include merging the nifi registry and minifi java into the nifi > > line itself. So when we release these things stay in sync and > > maintained. The release will now produce things like Apache NiFi, the > > Apache NiFi toolkit, Apache NiFi Registry, and Apache NiFi MiNiFi Java > > and the Apache NiFi stateless runtime as well. There have been many > > improvements to core nifi and stateless nifi now meaning we have the > > traditional execution form factor and this new stateless mode. We can > > now hot load nars from HDFS storage locations which could mean HDFS, > > blob storage in the cloud, etc.. There is a lot more. > > > > Anyway, I wanted to start circling the wagons for a 1.14 release. I'm > > happy to take on RM duties especially since there will be new elements > > to the release process. > > > > Thanks > >
