Re: [VOTE] Release Apache NiFi 1.15.0 (rc3)

[Marton Szasz]

+1 (binding)

Followed the release helper guide, tested systemd-journald message
collection from three minifi c++ linux agents to a single nifi
instance via putudp/listenudp.
Environment:
Apache Maven 3.8.3 (ff8e977a158738155dc465c6a97ffaf31982d739)
Maven home: /usr/share/maven-bin-3.8
Java version: 1.8.0_252, vendor: IcedTea, runtime: /opt/icedtea-bin-3.16.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.14.14-gentoo-x86_64", arch: "amd64",
family: "unix"

Marton

On Fri, 5 Nov 2021 at 21:33, Joey Frazee  wrote:
>
> +1 (binding)
>
> - Verified signatures and checksums (except for prior comment on minifi-c2)
> - Ran full build on Linux with Java 1.8.0_292
> - Ran various flows and ITs
> - Built and ran dockermaven Docker build
>
> -joey
>
> > On Nov 5, 2021, at 1:50 PM, Andrew Lim  wrote:
> >
> > +1 (binding)
> >
> > -Ran full clean install on OS X (Catalina 10.15.2, OpenJDK version 
> > 1.8.0_252)
> > -Tested secure NiFi with secure NiFi Registry
> > -Ran basic flows successfully; tested basic versioned flow functionality
> > -Reviewed UI fixes and documentation updates
> >
> > Drew
> >
> >> On Nov 3, 2021, at 3:29 PM, Joe Witt  wrote:
> >>
> >> Hello,
> >>
> >> I am pleased to be calling this vote for the source release of Apache
> >> NiFi 1.15.0.
> >>
> >> The source zip, including signatures, digests, etc. can be found at:
> >> https://repository.apache.org/content/repositories/orgapachenifi-1186
> >>
> >> The source being voted upon and the convenience binaries can be found at:
> >> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/
> >>
> >> A helpful reminder on how the release candidate verification process works:
> >> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> >>
> >> The Git tag is nifi-1.15.0-RC3
> >> The Git commit ID is 7fdc07cccdc0e23d4986557a9314e36859704a3b
> >> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=7fdc07cccdc0e23d4986557a9314e36859704a3b
> >>
> >> Checksums of nifi-1.15.0-source-release.zip:
> >> SHA256: 56fe317248941fdbc6216ec973e6ce898d0f682a54e2d063edbabf8542f5288a
> >> SHA512: 
> >> 63f10d9127cf1613c29bf2306be3d7a5b931b31304920706e0df5ea2fe87b58c410efed6ac37afc38d12c65e69f14aec7afb926000fc90cc13f15c738cd15c7f
> >>
> >> Release artifacts are signed with the following key:
> >> https://people.apache.org/keys/committer/joewitt.asc
> >>
> >> KEYS file available here:
> >> https://dist.apache.org/repos/dist/release/nifi/KEYS
> >>
> >> 234 issues were closed/resolved for this release:
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12350382
> >>
> >> Release note highlights can be found here:
> >> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.15.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-1.15.0
> >> [ ] +0 no opinion
> >> [ ] -1 Do not release this package because...
> >

Re: Not able to Enable controller service

[Mark Payne]

Hi Nilanjan,

Which Controller Service are you using? What version of NiFi? What do the logs 
show when you attempt to enable it? Have you tried restarting NiFi?

Thanks
-Mark


On Nov 5, 2021, at 7:07 AM, 
nilanjan.nandi2...@gmail.com wrote:

Hi Team ,

I am stuck in a weird situation where I am not able to enable a controller 
service , currently the controller service is disabled but when I try to enable 
it message pops out as can not enable due to the controller service is not 
disabled , please help on this




Please help , everything is default I just have changed jute.maxbuffer value to 
hold upto 9 mb data , other than that everything is default

Regards,
Nilanjan

Re: [VOTE] Release Apache NiFi 1.15.0 (rc3)

[Joey Frazee]

+1 (binding)

- Verified signatures and checksums (except for prior comment on minifi-c2)
- Ran full build on Linux with Java 1.8.0_292
- Ran various flows and ITs
- Built and ran dockermaven Docker build

-joey

> On Nov 5, 2021, at 1:50 PM, Andrew Lim  wrote:
> 
> +1 (binding)
> 
> -Ran full clean install on OS X (Catalina 10.15.2, OpenJDK version 1.8.0_252)
> -Tested secure NiFi with secure NiFi Registry
> -Ran basic flows successfully; tested basic versioned flow functionality
> -Reviewed UI fixes and documentation updates
> 
> Drew
> 
>> On Nov 3, 2021, at 3:29 PM, Joe Witt  wrote:
>> 
>> Hello,
>> 
>> I am pleased to be calling this vote for the source release of Apache
>> NiFi 1.15.0.
>> 
>> The source zip, including signatures, digests, etc. can be found at:
>> https://repository.apache.org/content/repositories/orgapachenifi-1186
>> 
>> The source being voted upon and the convenience binaries can be found at:
>> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/
>> 
>> A helpful reminder on how the release candidate verification process works:
>> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
>> 
>> The Git tag is nifi-1.15.0-RC3
>> The Git commit ID is 7fdc07cccdc0e23d4986557a9314e36859704a3b
>> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=7fdc07cccdc0e23d4986557a9314e36859704a3b
>> 
>> Checksums of nifi-1.15.0-source-release.zip:
>> SHA256: 56fe317248941fdbc6216ec973e6ce898d0f682a54e2d063edbabf8542f5288a
>> SHA512: 
>> 63f10d9127cf1613c29bf2306be3d7a5b931b31304920706e0df5ea2fe87b58c410efed6ac37afc38d12c65e69f14aec7afb926000fc90cc13f15c738cd15c7f
>> 
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/joewitt.asc
>> 
>> KEYS file available here:
>> https://dist.apache.org/repos/dist/release/nifi/KEYS
>> 
>> 234 issues were closed/resolved for this release:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12350382
>> 
>> Release note highlights can be found here:
>> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.15.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-1.15.0
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because...
> 

Re: [VOTE] Release Apache NiFi 1.15.0 (rc3)

[Andrew Lim]

+1 (binding)

-Ran full clean install on OS X (Catalina 10.15.2, OpenJDK version 1.8.0_252)
-Tested secure NiFi with secure NiFi Registry
-Ran basic flows successfully; tested basic versioned flow functionality
-Reviewed UI fixes and documentation updates

Drew

> On Nov 3, 2021, at 3:29 PM, Joe Witt  wrote:
> 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache
> NiFi 1.15.0.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1186
> 
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/
> 
> A helpful reminder on how the release candidate verification process works:
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> 
> The Git tag is nifi-1.15.0-RC3
> The Git commit ID is 7fdc07cccdc0e23d4986557a9314e36859704a3b
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=7fdc07cccdc0e23d4986557a9314e36859704a3b
> 
> Checksums of nifi-1.15.0-source-release.zip:
> SHA256: 56fe317248941fdbc6216ec973e6ce898d0f682a54e2d063edbabf8542f5288a
> SHA512: 
> 63f10d9127cf1613c29bf2306be3d7a5b931b31304920706e0df5ea2fe87b58c410efed6ac37afc38d12c65e69f14aec7afb926000fc90cc13f15c738cd15c7f
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 234 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12350382
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.15.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-1.15.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Re: [VOTE] Release Apache NiFi 1.15.0 (rc3)

[Mike Thomsen]

+1 binding. Ran through verification steps, build and run.

On Fri, Nov 5, 2021 at 11:29 AM Pierre Villard
 wrote:
>
> +1 (binding)
>
> Went through the usual steps, deployed a secured cluster with NiFi Registry
> on GCP, both configured with OIDC and using Azul JDK 11. Tested some of the
> new features and bug fixes. Looking good, this contains a lot of great
> stuff!
>
> Thanks for taking care of the release process Joe
>
> Thanks,
> Pierre
>
> Le ven. 5 nov. 2021 à 13:07, Chris Sampson
>  a écrit :
>
> > +1 (non-binding)
> >
> > - Built and ran from source on Ubuntu 20.04 (Windows 11 WSL2)
> > with AdoptOpenJDK-11.0.11+9
> > - Built and ran Docker Image (dockerhub) using the Dev Artifacts (from
> > re-based NIFI-8779 branch)
> >
> > - Verified Single User Authentication
> >
> > - Verified a few recent PRs via import and execution of a Flow definition
> > (S3 => Elasticsearch with some data manipulation in the middle)
> >
> >
> > Thanks for RM'ing Joe.
> >
> > ---
> > *Chris Sampson*
> > IT Consultant
> > chris.samp...@naimuri.com
> >
> >
> > On Fri, 5 Nov 2021 at 04:35, David Handermann  > >
> > wrote:
> >
> > > +1 (binding)
> > >
> > > - Built from source on Ubuntu 21.10 and macOS 11.6 with Azul Zulu 11.0.12
> > > and Azul Zulu 1.8.0.282
> > > - Ran NiFi on Azul Zulu 11.0.12 and 1.8.0.282
> > > - Verified Single User Authentication and OIDC Authentication with
> > Keycloak
> > > - Verified updates to JWT client storage and cookie handling
> > > - Verified basic operation of NiFi Regstriy
> > >
> > > - NIFI-6617 Verified encrypted repository configuration using new
> > > properties with BCFKS and PKCS12 KeyStores
> > > - NIFI-7322 Verified SignContentPGP and VerifyContentPGP together with
> > > EncryptContentPGP and DecryptContentPGP using various properties
> > > - NIFI-8424 Verified absence of HtmlDocumentWriter warnings on startup
> > > - NIFI-8943 Built, launched, and restarted Docker container verifying
> > > persistence of random sensitive properties key
> > > - NIFI-9059 Ran simple data flow using NiFi Stateless on Java 11
> > > - NIFI-9223 Verified ListenSyslog listens on 0.0.0.0 using default
> > > properties
> > > - NIFI-9251 Verified absence of unused generated password in NiFi
> > Registry
> > > - NIFI-9266 Verified Azure Key Vault Secret Sensitive Property Provider
> > > configuration for nifi.properties
> > > - NIFI-9322 Verified corrected REST API documentation for OIDC and SAML
> > > resources
> > > - NIFI-9339 Verified JoltTransformJSON custom UI works as expected
> > >
> > > Thanks for managing the release process Joe!
> > >
> > > Regards,
> > > David Handermann
> > >
> > >
> > >
> > >
> > > On Thu, Nov 4, 2021 at 6:33 PM Matt Burgess 
> > wrote:
> > >
> > > > +1 Release this package as nifi-1.15.0
> > > >
> > > > Ran through the release helper and some tests to verify various Jiras
> > > > were included. Thanks again for RM'ing Joe!
> > > >
> > > > On Wed, Nov 3, 2021 at 3:29 PM Joe Witt  wrote:
> > > > >
> > > > > Hello,
> > > > >
> > > > > I am pleased to be calling this vote for the source release of Apache
> > > > > NiFi 1.15.0.
> > > > >
> > > > > The source zip, including signatures, digests, etc. can be found at:
> > > > >
> > https://repository.apache.org/content/repositories/orgapachenifi-1186
> > > > >
> > > > > The source being voted upon and the convenience binaries can be found
> > > at:
> > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/
> > > > >
> > > > > A helpful reminder on how the release candidate verification process
> > > > works:
> > > > >
> > > >
> > >
> > https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> > > > >
> > > > > The Git tag is nifi-1.15.0-RC3
> > > > > The Git commit ID is 7fdc07cccdc0e23d4986557a9314e36859704a3b
> > > > >
> > > >
> > >
> > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=7fdc07cccdc0e23d4986557a9314e36859704a3b
> > > > >
> > > > > Checksums of nifi-1.15.0-source-release.zip:
> > > > > SHA256:
> > > 56fe317248941fdbc6216ec973e6ce898d0f682a54e2d063edbabf8542f5288a
> > > > > SHA512:
> > > >
> > >
> > 63f10d9127cf1613c29bf2306be3d7a5b931b31304920706e0df5ea2fe87b58c410efed6ac37afc38d12c65e69f14aec7afb926000fc90cc13f15c738cd15c7f
> > > > >
> > > > > Release artifacts are signed with the following key:
> > > > > https://people.apache.org/keys/committer/joewitt.asc
> > > > >
> > > > > KEYS file available here:
> > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > > >
> > > > > 234 issues were closed/resolved for this release:
> > > > >
> > > >
> > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12350382
> > > > >
> > > > > Release note highlights can be found here:
> > > > >
> > > >
> > >
> > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.15.0
> > > > >
> > > > > The vote will be open for 72 hours.
> > > > > Please download the release candidate and evaluate the necessary
> > 

Re: [VOTE] Release Apache NiFi 1.15.0 (rc3)

[Joey Frazee]

JFYI, the .sha256 files for minifi-c2 are wrong/actually sha512.

One interpretation of the release policy is that those aren’t being voted on 
and just for verification, so provided it’s fixed before the release gets 
checked in it might be ok.

-joey

> On Nov 5, 2021, at 8:29 AM, Pierre Villard  
> wrote:
> 
> +1 (binding)
> 
> Went through the usual steps, deployed a secured cluster with NiFi Registry
> on GCP, both configured with OIDC and using Azul JDK 11. Tested some of the
> new features and bug fixes. Looking good, this contains a lot of great
> stuff!
> 
> Thanks for taking care of the release process Joe
> 
> Thanks,
> Pierre
> 
>> Le ven. 5 nov. 2021 à 13:07, Chris Sampson
>>  a écrit :
>> 
>> +1 (non-binding)
>> 
>> - Built and ran from source on Ubuntu 20.04 (Windows 11 WSL2)
>> with AdoptOpenJDK-11.0.11+9
>> - Built and ran Docker Image (dockerhub) using the Dev Artifacts (from
>> re-based NIFI-8779 branch)
>> 
>> - Verified Single User Authentication
>> 
>> - Verified a few recent PRs via import and execution of a Flow definition
>> (S3 => Elasticsearch with some data manipulation in the middle)
>> 
>> 
>> Thanks for RM'ing Joe.
>> 
>> ---
>> *Chris Sampson*
>> IT Consultant
>> chris.samp...@naimuri.com
>> 
>> 
>> On Fri, 5 Nov 2021 at 04:35, David Handermann >> 
>> wrote:
>> 
>>> +1 (binding)
>>> 
>>> - Built from source on Ubuntu 21.10 and macOS 11.6 with Azul Zulu 11.0.12
>>> and Azul Zulu 1.8.0.282
>>> - Ran NiFi on Azul Zulu 11.0.12 and 1.8.0.282
>>> - Verified Single User Authentication and OIDC Authentication with
>> Keycloak
>>> - Verified updates to JWT client storage and cookie handling
>>> - Verified basic operation of NiFi Regstriy
>>> 
>>> - NIFI-6617 Verified encrypted repository configuration using new
>>> properties with BCFKS and PKCS12 KeyStores
>>> - NIFI-7322 Verified SignContentPGP and VerifyContentPGP together with
>>> EncryptContentPGP and DecryptContentPGP using various properties
>>> - NIFI-8424 Verified absence of HtmlDocumentWriter warnings on startup
>>> - NIFI-8943 Built, launched, and restarted Docker container verifying
>>> persistence of random sensitive properties key
>>> - NIFI-9059 Ran simple data flow using NiFi Stateless on Java 11
>>> - NIFI-9223 Verified ListenSyslog listens on 0.0.0.0 using default
>>> properties
>>> - NIFI-9251 Verified absence of unused generated password in NiFi
>> Registry
>>> - NIFI-9266 Verified Azure Key Vault Secret Sensitive Property Provider
>>> configuration for nifi.properties
>>> - NIFI-9322 Verified corrected REST API documentation for OIDC and SAML
>>> resources
>>> - NIFI-9339 Verified JoltTransformJSON custom UI works as expected
>>> 
>>> Thanks for managing the release process Joe!
>>> 
>>> Regards,
>>> David Handermann
>>> 
>>> 
>>> 
>>> 
>>> On Thu, Nov 4, 2021 at 6:33 PM Matt Burgess 
>> wrote:
>>> 
 +1 Release this package as nifi-1.15.0
 
 Ran through the release helper and some tests to verify various Jiras
 were included. Thanks again for RM'ing Joe!
 
 On Wed, Nov 3, 2021 at 3:29 PM Joe Witt  wrote:
> 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache
> NiFi 1.15.0.
> 
> The source zip, including signatures, digests, etc. can be found at:
> 
>> https://repository.apache.org/content/repositories/orgapachenifi-1186
> 
> The source being voted upon and the convenience binaries can be found
>>> at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/
> 
> A helpful reminder on how the release candidate verification process
 works:
> 
 
>>> 
>> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> 
> The Git tag is nifi-1.15.0-RC3
> The Git commit ID is 7fdc07cccdc0e23d4986557a9314e36859704a3b
> 
 
>>> 
>> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=7fdc07cccdc0e23d4986557a9314e36859704a3b
> 
> Checksums of nifi-1.15.0-source-release.zip:
> SHA256:
>>> 56fe317248941fdbc6216ec973e6ce898d0f682a54e2d063edbabf8542f5288a
> SHA512:
 
>>> 
>> 63f10d9127cf1613c29bf2306be3d7a5b931b31304920706e0df5ea2fe87b58c410efed6ac37afc38d12c65e69f14aec7afb926000fc90cc13f15c738cd15c7f
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 234 issues were closed/resolved for this release:
> 
 
>>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12350382
> 
> Release note highlights can be found here:
> 
 
>>> 
>> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.15.0
> 
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary
>> items
> including checking hashes, signatures, build 

Re: [VOTE] Release Apache NiFi 1.15.0 (rc3)

[Pierre Villard]

+1 (binding)

Went through the usual steps, deployed a secured cluster with NiFi Registry
on GCP, both configured with OIDC and using Azul JDK 11. Tested some of the
new features and bug fixes. Looking good, this contains a lot of great
stuff!

Thanks for taking care of the release process Joe

Thanks,
Pierre

Le ven. 5 nov. 2021 à 13:07, Chris Sampson
 a écrit :

> +1 (non-binding)
>
> - Built and ran from source on Ubuntu 20.04 (Windows 11 WSL2)
> with AdoptOpenJDK-11.0.11+9
> - Built and ran Docker Image (dockerhub) using the Dev Artifacts (from
> re-based NIFI-8779 branch)
>
> - Verified Single User Authentication
>
> - Verified a few recent PRs via import and execution of a Flow definition
> (S3 => Elasticsearch with some data manipulation in the middle)
>
>
> Thanks for RM'ing Joe.
>
> ---
> *Chris Sampson*
> IT Consultant
> chris.samp...@naimuri.com
>
>
> On Fri, 5 Nov 2021 at 04:35, David Handermann  >
> wrote:
>
> > +1 (binding)
> >
> > - Built from source on Ubuntu 21.10 and macOS 11.6 with Azul Zulu 11.0.12
> > and Azul Zulu 1.8.0.282
> > - Ran NiFi on Azul Zulu 11.0.12 and 1.8.0.282
> > - Verified Single User Authentication and OIDC Authentication with
> Keycloak
> > - Verified updates to JWT client storage and cookie handling
> > - Verified basic operation of NiFi Regstriy
> >
> > - NIFI-6617 Verified encrypted repository configuration using new
> > properties with BCFKS and PKCS12 KeyStores
> > - NIFI-7322 Verified SignContentPGP and VerifyContentPGP together with
> > EncryptContentPGP and DecryptContentPGP using various properties
> > - NIFI-8424 Verified absence of HtmlDocumentWriter warnings on startup
> > - NIFI-8943 Built, launched, and restarted Docker container verifying
> > persistence of random sensitive properties key
> > - NIFI-9059 Ran simple data flow using NiFi Stateless on Java 11
> > - NIFI-9223 Verified ListenSyslog listens on 0.0.0.0 using default
> > properties
> > - NIFI-9251 Verified absence of unused generated password in NiFi
> Registry
> > - NIFI-9266 Verified Azure Key Vault Secret Sensitive Property Provider
> > configuration for nifi.properties
> > - NIFI-9322 Verified corrected REST API documentation for OIDC and SAML
> > resources
> > - NIFI-9339 Verified JoltTransformJSON custom UI works as expected
> >
> > Thanks for managing the release process Joe!
> >
> > Regards,
> > David Handermann
> >
> >
> >
> >
> > On Thu, Nov 4, 2021 at 6:33 PM Matt Burgess 
> wrote:
> >
> > > +1 Release this package as nifi-1.15.0
> > >
> > > Ran through the release helper and some tests to verify various Jiras
> > > were included. Thanks again for RM'ing Joe!
> > >
> > > On Wed, Nov 3, 2021 at 3:29 PM Joe Witt  wrote:
> > > >
> > > > Hello,
> > > >
> > > > I am pleased to be calling this vote for the source release of Apache
> > > > NiFi 1.15.0.
> > > >
> > > > The source zip, including signatures, digests, etc. can be found at:
> > > >
> https://repository.apache.org/content/repositories/orgapachenifi-1186
> > > >
> > > > The source being voted upon and the convenience binaries can be found
> > at:
> > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/
> > > >
> > > > A helpful reminder on how the release candidate verification process
> > > works:
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> > > >
> > > > The Git tag is nifi-1.15.0-RC3
> > > > The Git commit ID is 7fdc07cccdc0e23d4986557a9314e36859704a3b
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=7fdc07cccdc0e23d4986557a9314e36859704a3b
> > > >
> > > > Checksums of nifi-1.15.0-source-release.zip:
> > > > SHA256:
> > 56fe317248941fdbc6216ec973e6ce898d0f682a54e2d063edbabf8542f5288a
> > > > SHA512:
> > >
> >
> 63f10d9127cf1613c29bf2306be3d7a5b931b31304920706e0df5ea2fe87b58c410efed6ac37afc38d12c65e69f14aec7afb926000fc90cc13f15c738cd15c7f
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/joewitt.asc
> > > >
> > > > KEYS file available here:
> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > >
> > > > 234 issues were closed/resolved for this release:
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12350382
> > > >
> > > > Release note highlights can be found here:
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.15.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-1.15.0
> > > > [ ] +0 no opinion
> > > > [ ] -1 Do not release this package because...
> > >
> >
>

Re: [VOTE] Release Apache NiFi 1.15.0 (rc3)

[Mark Payne]

+1 (binding)

- Verified hashes
- Performed full build with all unit test / contrib check
- Ran all system tests
- Testing some of the new key features


On 2021/11/03 19:29:21, Joe Witt  wrote: 
> Hello,> 
> 
> I am pleased to be calling this vote for the source release of Apache> 
> NiFi 1.15.0.> 
> 
> The source zip, including signatures, digests, etc. can be found at:> 
> https://repository.apache.org/content/repositories/orgapachenifi-1186> 
> 
> The source being voted upon and the convenience binaries can be found at:> 
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/> 
> 
> A helpful reminder on how the release candidate verification process works:> 
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate>
>  
> 
> The Git tag is nifi-1.15.0-RC3> 
> The Git commit ID is 7fdc07cccdc0e23d4986557a9314e36859704a3b> 
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=7fdc07cccdc0e23d4986557a9314e36859704a3b>
>  
> 
> Checksums of nifi-1.15.0-source-release.zip:> 
> SHA256: 56fe317248941fdbc6216ec973e6ce898d0f682a54e2d063edbabf8542f5288a> 
> SHA512: 
> 63f10d9127cf1613c29bf2306be3d7a5b931b31304920706e0df5ea2fe87b58c410efed6ac37afc38d12c65e69f14aec7afb926000fc90cc13f15c738cd15c7f>
>  
> 
> Release artifacts are signed with the following key:> 
> https://people.apache.org/keys/committer/joewitt.asc> 
> 
> KEYS file available here:> 
> https://dist.apache.org/repos/dist/release/nifi/KEYS> 
> 
> 234 issues were closed/resolved for this release:> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12350382>
>  
> 
> Release note highlights can be found here:> 
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.15.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-1.15.0> 
> [ ] +0 no opinion> 
> [ ] -1 Do not release this package because...> 
> 

Re: [discuss] NiFi 1.15

[David Handermann]

Thanks for the update Chris!

I agree with the suggestion to streamline the Dockerfiles for NiFi builds,
there is a lot of duplication between dockermaven and dockerhub, so
unifying the modules and parameterizing necessary differences would be a
helpful improvement.

Regards,
David Handermann

On Fri, Nov 5, 2021 at 9:10 AM Kevin Doran  wrote:

> Hi Chris,
>
> Thanks for the summary of your findings.
>
> I agree that we should clear up our process for generating Docker images
> and that the process should be consistent as possible across NiFi, MiNiFi
> Java, Registry, and Toolkit given they are all part of the same repository
> and maven project. This will clear up confusion and improve
> maintainability.
>
> I think both of these methods are important and useful:
>
> 1. building from downloaded convenience binaries for previously released
> versions
> 2. building from a local assembly output
>
> That said, I think we could probably consolidate to a single Dockerfile
> that takes the binary location as an argument that supports either a URL or
> local file path (or a version which could default to the current behavior
> of inferring a URL location). This would let us continue to support the
> flexibility we have today while maintaining a single Docker file rather
> than dockermaven and dockerhub variants. If you and others on the list
> agree, I can open up a Jira summarizing what needs to be done.
>
> Thanks,
> Kevin
>
> > On Nov 5, 2021, at 05:00, Chris Sampson 
> wrote:
> >
> > So the good news is that I realised what I was doing wrong yesterday -
> I'd
> > started a local installation after building the RC, then not shut that
> down
> > before booting up the Docker instance, so the username/password I was
> > trying to use from the Docker logs was wrong against the local
> > installation, d'oh!
> >
> > Having corrected that this morning, I've successfully booted up and
> logged
> > into a Docker instance built using the RC (with my NIFI-8779 changes so I
> > could build from the Dev server instead of the main Apache Archive).
> >
> > The reason the dockermaven build works is that it uses the locally built
> > archive files (i.e. you have to do a full Maven build locally first to
> > generate the ZIP files and then create teh Docker image). The
> > dockerhub build actually downloads published artifacts from the Apache
> > servers - to do this the Dockerfile needs to know the exact path to the
> > artifacts it's trying to download, of course.
> >
> > There was a question recently in one of the Slack channels about whether
> > both of these builds (dockerhub and dockermaven) were still valid/needed
> -
> > I think Joe replied that he wasn't sure (Docker not being an area he
> > ventures into much, which is fair enough). It may be worth considering
> > whether these two modules are both still needed or can be rationalised
> and
> > if the latter, which approach should be used - download from the archive
> > server or build from local (both have dis/advantages, but the more
> > "official" way is arguably to download from the server).
> >
> > Also maybe worth noting:
> > * NiFi Registry only has the "build from local" Dockerfile setup
> > * MiniFi (Java) has both local and archive download options, but the
> latter
> > cannot be used to build an image from the Dev server (the BASE_URL cannot
> > be changed via a build arg/env var... this is the issue addressed by
> > NIFI-8779 for NiFi)
> > * NiFi Toolkit has both local and archive download options, but are
> located
> > in a single assembly module (instead of split into two like NiFi and
> MiniFi)
> >
> > Assuming the "nifi/" path will be used for the actual release
> > artifacts, this shouldn't be a blocker, but it's one to note/remember
> when
> > the time comes (assuming the "dockerhub" module is what's used to publish
> > the "apache/nifi" image to Docker Hub that is).
> >
> >
> > ---
> > *Chris Sampson*
> > IT Consultant
> > chris.samp...@naimuri.com
> >
> >
> > On Fri, 5 Nov 2021 at 03:34, David Handermann <
> exceptionfact...@apache.org>
> > wrote:
> >
> >> Chris,
> >>
> >> I am running through several verification steps, but I built 1.15.0 RC 3
> >> from sources and then ran "mvn install -pl :dockermaven -P docker" to
> build
> >> the Docker image.  When starting with the following command, I was able
> to
> >> use the generated username and password to access the running NiFi
> >> container:
> >>
> >> docker run --name nifi -p 8443:8443 apache/nifi:1.15.0-dockermaven
> >>
> >> If you are still having issues, it would be helpful to provide any logs
> or
> >> error messages you are seeing.
> >>
> >> Regards,
> >> David Handermann
> >>
> >> On Thu, Nov 4, 2021 at 8:10 PM Kevin Doran 
> >> wrote:
> >>
> >>> Oh meant to send a link to this too:
> >>>
>  ARG
> >>>
> >>
> NIFI_BINARY_PATH=${NIFI_BINARY_PATH:-/nifi/${NIFI_VERSION}/nifi-${NIFI_VERSION}-bin.zip}
> >>>
> >>>
> >>>
> >>
> 

Re: [discuss] NiFi 1.15

[Chris Sampson]

Kevin,

Sounds sensible to me, thanks!


---
*Chris Sampson*
IT Consultant
chris.samp...@naimuri.com


On Fri, 5 Nov 2021 at 14:10, Kevin Doran  wrote:

> Hi Chris,
>
> Thanks for the summary of your findings.
>
> I agree that we should clear up our process for generating Docker images
> and that the process should be consistent as possible across NiFi, MiNiFi
> Java, Registry, and Toolkit given they are all part of the same repository
> and maven project. This will clear up confusion and improve
> maintainability.
>
> I think both of these methods are important and useful:
>
> 1. building from downloaded convenience binaries for previously released
> versions
> 2. building from a local assembly output
>
> That said, I think we could probably consolidate to a single Dockerfile
> that takes the binary location as an argument that supports either a URL or
> local file path (or a version which could default to the current behavior
> of inferring a URL location). This would let us continue to support the
> flexibility we have today while maintaining a single Docker file rather
> than dockermaven and dockerhub variants. If you and others on the list
> agree, I can open up a Jira summarizing what needs to be done.
>
> Thanks,
> Kevin
>
> > On Nov 5, 2021, at 05:00, Chris Sampson 
> wrote:
> >
> > So the good news is that I realised what I was doing wrong yesterday -
> I'd
> > started a local installation after building the RC, then not shut that
> down
> > before booting up the Docker instance, so the username/password I was
> > trying to use from the Docker logs was wrong against the local
> > installation, d'oh!
> >
> > Having corrected that this morning, I've successfully booted up and
> logged
> > into a Docker instance built using the RC (with my NIFI-8779 changes so I
> > could build from the Dev server instead of the main Apache Archive).
> >
> > The reason the dockermaven build works is that it uses the locally built
> > archive files (i.e. you have to do a full Maven build locally first to
> > generate the ZIP files and then create teh Docker image). The
> > dockerhub build actually downloads published artifacts from the Apache
> > servers - to do this the Dockerfile needs to know the exact path to the
> > artifacts it's trying to download, of course.
> >
> > There was a question recently in one of the Slack channels about whether
> > both of these builds (dockerhub and dockermaven) were still valid/needed
> -
> > I think Joe replied that he wasn't sure (Docker not being an area he
> > ventures into much, which is fair enough). It may be worth considering
> > whether these two modules are both still needed or can be rationalised
> and
> > if the latter, which approach should be used - download from the archive
> > server or build from local (both have dis/advantages, but the more
> > "official" way is arguably to download from the server).
> >
> > Also maybe worth noting:
> > * NiFi Registry only has the "build from local" Dockerfile setup
> > * MiniFi (Java) has both local and archive download options, but the
> latter
> > cannot be used to build an image from the Dev server (the BASE_URL cannot
> > be changed via a build arg/env var... this is the issue addressed by
> > NIFI-8779 for NiFi)
> > * NiFi Toolkit has both local and archive download options, but are
> located
> > in a single assembly module (instead of split into two like NiFi and
> MiniFi)
> >
> > Assuming the "nifi/" path will be used for the actual release
> > artifacts, this shouldn't be a blocker, but it's one to note/remember
> when
> > the time comes (assuming the "dockerhub" module is what's used to publish
> > the "apache/nifi" image to Docker Hub that is).
> >
> >
> > ---
> > *Chris Sampson*
> > IT Consultant
> > chris.samp...@naimuri.com
> >
> >
> > On Fri, 5 Nov 2021 at 03:34, David Handermann <
> exceptionfact...@apache.org>
> > wrote:
> >
> >> Chris,
> >>
> >> I am running through several verification steps, but I built 1.15.0 RC 3
> >> from sources and then ran "mvn install -pl :dockermaven -P docker" to
> build
> >> the Docker image.  When starting with the following command, I was able
> to
> >> use the generated username and password to access the running NiFi
> >> container:
> >>
> >> docker run --name nifi -p 8443:8443 apache/nifi:1.15.0-dockermaven
> >>
> >> If you are still having issues, it would be helpful to provide any logs
> or
> >> error messages you are seeing.
> >>
> >> Regards,
> >> David Handermann
> >>
> >> On Thu, Nov 4, 2021 at 8:10 PM Kevin Doran 
> >> wrote:
> >>
> >>> Oh meant to send a link to this too:
> >>>
>  ARG
> >>>
> >>
> NIFI_BINARY_PATH=${NIFI_BINARY_PATH:-/nifi/${NIFI_VERSION}/nifi-${NIFI_VERSION}-bin.zip}
> >>>
> >>>
> >>>
> >>
> https://github.com/apache/nifi/blob/373498445fe589e2d4855a0730fbb9127f0b4452/nifi-docker/dockerhub/Dockerfile#L30
> >>>
>  On Nov 4, 2021, at 9:09 PM, Kevin Doran 
> >> wrote:
> 
>  Hi Joe and Chris,
> 
>  Our Dockerfile that we use to build 

Re: [discuss] NiFi 1.15

[Kevin Doran]

Hi Chris,

Thanks for the summary of your findings.

I agree that we should clear up our process for generating Docker images and 
that the process should be consistent as possible across NiFi, MiNiFi Java, 
Registry, and Toolkit given they are all part of the same repository and maven 
project. This will clear up confusion and improve maintainability. 

I think both of these methods are important and useful:

1. building from downloaded convenience binaries for previously released 
versions
2. building from a local assembly output

That said, I think we could probably consolidate to a single Dockerfile that 
takes the binary location as an argument that supports either a URL or local 
file path (or a version which could default to the current behavior of 
inferring a URL location). This would let us continue to support the 
flexibility we have today while maintaining a single Docker file rather than 
dockermaven and dockerhub variants. If you and others on the list agree, I can 
open up a Jira summarizing what needs to be done.

Thanks,
Kevin

> On Nov 5, 2021, at 05:00, Chris Sampson  
> wrote:
> 
> So the good news is that I realised what I was doing wrong yesterday - I'd
> started a local installation after building the RC, then not shut that down
> before booting up the Docker instance, so the username/password I was
> trying to use from the Docker logs was wrong against the local
> installation, d'oh!
> 
> Having corrected that this morning, I've successfully booted up and logged
> into a Docker instance built using the RC (with my NIFI-8779 changes so I
> could build from the Dev server instead of the main Apache Archive).
> 
> The reason the dockermaven build works is that it uses the locally built
> archive files (i.e. you have to do a full Maven build locally first to
> generate the ZIP files and then create teh Docker image). The
> dockerhub build actually downloads published artifacts from the Apache
> servers - to do this the Dockerfile needs to know the exact path to the
> artifacts it's trying to download, of course.
> 
> There was a question recently in one of the Slack channels about whether
> both of these builds (dockerhub and dockermaven) were still valid/needed -
> I think Joe replied that he wasn't sure (Docker not being an area he
> ventures into much, which is fair enough). It may be worth considering
> whether these two modules are both still needed or can be rationalised and
> if the latter, which approach should be used - download from the archive
> server or build from local (both have dis/advantages, but the more
> "official" way is arguably to download from the server).
> 
> Also maybe worth noting:
> * NiFi Registry only has the "build from local" Dockerfile setup
> * MiniFi (Java) has both local and archive download options, but the latter
> cannot be used to build an image from the Dev server (the BASE_URL cannot
> be changed via a build arg/env var... this is the issue addressed by
> NIFI-8779 for NiFi)
> * NiFi Toolkit has both local and archive download options, but are located
> in a single assembly module (instead of split into two like NiFi and MiniFi)
> 
> Assuming the "nifi/" path will be used for the actual release
> artifacts, this shouldn't be a blocker, but it's one to note/remember when
> the time comes (assuming the "dockerhub" module is what's used to publish
> the "apache/nifi" image to Docker Hub that is).
> 
> 
> ---
> *Chris Sampson*
> IT Consultant
> chris.samp...@naimuri.com
> 
> 
> On Fri, 5 Nov 2021 at 03:34, David Handermann 
> wrote:
> 
>> Chris,
>> 
>> I am running through several verification steps, but I built 1.15.0 RC 3
>> from sources and then ran "mvn install -pl :dockermaven -P docker" to build
>> the Docker image.  When starting with the following command, I was able to
>> use the generated username and password to access the running NiFi
>> container:
>> 
>> docker run --name nifi -p 8443:8443 apache/nifi:1.15.0-dockermaven
>> 
>> If you are still having issues, it would be helpful to provide any logs or
>> error messages you are seeing.
>> 
>> Regards,
>> David Handermann
>> 
>> On Thu, Nov 4, 2021 at 8:10 PM Kevin Doran 
>> wrote:
>> 
>>> Oh meant to send a link to this too:
>>> 
 ARG
>>> 
>> NIFI_BINARY_PATH=${NIFI_BINARY_PATH:-/nifi/${NIFI_VERSION}/nifi-${NIFI_VERSION}-bin.zip}
>>> 
>>> 
>>> 
>> https://github.com/apache/nifi/blob/373498445fe589e2d4855a0730fbb9127f0b4452/nifi-docker/dockerhub/Dockerfile#L30
>>> 
 On Nov 4, 2021, at 9:09 PM, Kevin Doran 
>> wrote:
 
 Hi Joe and Chris,
 
 Our Dockerfile that we use to build the Dockerhub image defaults to
>>> looking for 1.15.0 instead of NiFi-1.15.0, but it is a variable that we
>> can
>>> override, so this is easy to workaround incase the release folder does
>>> change. Agree its nice to keep the tree structure consistent when we can.
 
 I’m about to do my verification and will also check the single user
>> with
>>> the docker image as part of that.

Not able to Enable controller service

[nilanjan . nandi2910]

Hi Team ,

I am stuck in a weird situation where I am not able to enable a controller 
service , currently the controller service is disabled but when I try to enable 
it message pops out as can not enable due to the controller service is not 
disabled , please help on this




Please help , everything is default I just have changed jute.maxbuffer value to 
hold upto 9 mb data , other than that everything is default

Regards,
Nilanjan

Re: [VOTE] Release Apache NiFi 1.15.0 (rc3)

[Chris Sampson]

+1 (non-binding)

- Built and ran from source on Ubuntu 20.04 (Windows 11 WSL2)
with AdoptOpenJDK-11.0.11+9
- Built and ran Docker Image (dockerhub) using the Dev Artifacts (from
re-based NIFI-8779 branch)

- Verified Single User Authentication

- Verified a few recent PRs via import and execution of a Flow definition
(S3 => Elasticsearch with some data manipulation in the middle)


Thanks for RM'ing Joe.

---
*Chris Sampson*
IT Consultant
chris.samp...@naimuri.com


On Fri, 5 Nov 2021 at 04:35, David Handermann 
wrote:

> +1 (binding)
>
> - Built from source on Ubuntu 21.10 and macOS 11.6 with Azul Zulu 11.0.12
> and Azul Zulu 1.8.0.282
> - Ran NiFi on Azul Zulu 11.0.12 and 1.8.0.282
> - Verified Single User Authentication and OIDC Authentication with Keycloak
> - Verified updates to JWT client storage and cookie handling
> - Verified basic operation of NiFi Regstriy
>
> - NIFI-6617 Verified encrypted repository configuration using new
> properties with BCFKS and PKCS12 KeyStores
> - NIFI-7322 Verified SignContentPGP and VerifyContentPGP together with
> EncryptContentPGP and DecryptContentPGP using various properties
> - NIFI-8424 Verified absence of HtmlDocumentWriter warnings on startup
> - NIFI-8943 Built, launched, and restarted Docker container verifying
> persistence of random sensitive properties key
> - NIFI-9059 Ran simple data flow using NiFi Stateless on Java 11
> - NIFI-9223 Verified ListenSyslog listens on 0.0.0.0 using default
> properties
> - NIFI-9251 Verified absence of unused generated password in NiFi Registry
> - NIFI-9266 Verified Azure Key Vault Secret Sensitive Property Provider
> configuration for nifi.properties
> - NIFI-9322 Verified corrected REST API documentation for OIDC and SAML
> resources
> - NIFI-9339 Verified JoltTransformJSON custom UI works as expected
>
> Thanks for managing the release process Joe!
>
> Regards,
> David Handermann
>
>
>
>
> On Thu, Nov 4, 2021 at 6:33 PM Matt Burgess  wrote:
>
> > +1 Release this package as nifi-1.15.0
> >
> > Ran through the release helper and some tests to verify various Jiras
> > were included. Thanks again for RM'ing Joe!
> >
> > On Wed, Nov 3, 2021 at 3:29 PM Joe Witt  wrote:
> > >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi 1.15.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1186
> > >
> > > The source being voted upon and the convenience binaries can be found
> at:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.0/
> > >
> > > A helpful reminder on how the release candidate verification process
> > works:
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> > >
> > > The Git tag is nifi-1.15.0-RC3
> > > The Git commit ID is 7fdc07cccdc0e23d4986557a9314e36859704a3b
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=7fdc07cccdc0e23d4986557a9314e36859704a3b
> > >
> > > Checksums of nifi-1.15.0-source-release.zip:
> > > SHA256:
> 56fe317248941fdbc6216ec973e6ce898d0f682a54e2d063edbabf8542f5288a
> > > SHA512:
> >
> 63f10d9127cf1613c29bf2306be3d7a5b931b31304920706e0df5ea2fe87b58c410efed6ac37afc38d12c65e69f14aec7afb926000fc90cc13f15c738cd15c7f
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/joewitt.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 234 issues were closed/resolved for this release:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12350382
> > >
> > > Release note highlights can be found here:
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.15.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-1.15.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> >
>

Re: [discuss] NiFi 1.15

[Chris Sampson]

So the good news is that I realised what I was doing wrong yesterday - I'd
started a local installation after building the RC, then not shut that down
before booting up the Docker instance, so the username/password I was
trying to use from the Docker logs was wrong against the local
installation, d'oh!

Having corrected that this morning, I've successfully booted up and logged
into a Docker instance built using the RC (with my NIFI-8779 changes so I
could build from the Dev server instead of the main Apache Archive).

The reason the dockermaven build works is that it uses the locally built
archive files (i.e. you have to do a full Maven build locally first to
generate the ZIP files and then create teh Docker image). The
dockerhub build actually downloads published artifacts from the Apache
servers - to do this the Dockerfile needs to know the exact path to the
artifacts it's trying to download, of course.

There was a question recently in one of the Slack channels about whether
both of these builds (dockerhub and dockermaven) were still valid/needed -
I think Joe replied that he wasn't sure (Docker not being an area he
ventures into much, which is fair enough). It may be worth considering
whether these two modules are both still needed or can be rationalised and
if the latter, which approach should be used - download from the archive
server or build from local (both have dis/advantages, but the more
"official" way is arguably to download from the server).

Also maybe worth noting:
* NiFi Registry only has the "build from local" Dockerfile setup
* MiniFi (Java) has both local and archive download options, but the latter
cannot be used to build an image from the Dev server (the BASE_URL cannot
be changed via a build arg/env var... this is the issue addressed by
NIFI-8779 for NiFi)
* NiFi Toolkit has both local and archive download options, but are located
in a single assembly module (instead of split into two like NiFi and MiniFi)

Assuming the "nifi/" path will be used for the actual release
artifacts, this shouldn't be a blocker, but it's one to note/remember when
the time comes (assuming the "dockerhub" module is what's used to publish
the "apache/nifi" image to Docker Hub that is).


---
*Chris Sampson*
IT Consultant
chris.samp...@naimuri.com


On Fri, 5 Nov 2021 at 03:34, David Handermann 
wrote:

> Chris,
>
> I am running through several verification steps, but I built 1.15.0 RC 3
> from sources and then ran "mvn install -pl :dockermaven -P docker" to build
> the Docker image.  When starting with the following command, I was able to
> use the generated username and password to access the running NiFi
> container:
>
> docker run --name nifi -p 8443:8443 apache/nifi:1.15.0-dockermaven
>
> If you are still having issues, it would be helpful to provide any logs or
> error messages you are seeing.
>
> Regards,
> David Handermann
>
> On Thu, Nov 4, 2021 at 8:10 PM Kevin Doran 
> wrote:
>
> > Oh meant to send a link to this too:
> >
> > > ARG
> >
> NIFI_BINARY_PATH=${NIFI_BINARY_PATH:-/nifi/${NIFI_VERSION}/nifi-${NIFI_VERSION}-bin.zip}
> >
> >
> >
> https://github.com/apache/nifi/blob/373498445fe589e2d4855a0730fbb9127f0b4452/nifi-docker/dockerhub/Dockerfile#L30
> >
> > > On Nov 4, 2021, at 9:09 PM, Kevin Doran 
> wrote:
> > >
> > > Hi Joe and Chris,
> > >
> > > Our Dockerfile that we use to build the Dockerhub image defaults to
> > looking for 1.15.0 instead of NiFi-1.15.0, but it is a variable that we
> can
> > override, so this is easy to workaround incase the release folder does
> > change. Agree its nice to keep the tree structure consistent when we can.
> > >
> > > I’m about to do my verification and will also check the single user
> with
> > the docker image as part of that.
> > >
> > > Cheers,
> > > Kevin
> > >
> > >> On Nov 4, 2021, at 6:44 PM, Joe Witt  wrote:
> > >>
> > >> Chris,
> > >>
> > >> Yeah I should have just put it in 1.15.0 instead of nifi/1.15.0.
> > >> Should generally not really matter so the docker angle there is
> > >> interesting.  Not sure why our docker images would have any
> > >> relationship to our dist/dev storage.  But when I move them into the
> > >> release folder I can try to ensure I place them only in 1.15.0 instead
> > >> of nifi/1.15.0.
> > >>
> > >> That directory the prov stuff makes does linger and can be annoying so
> > >> thanks for tackling that.  Saw the PR.  Will take a look soon if
> > >> nobody else has.
> > >>
> > >> Will keep an eye on your findings related to docker builds not working
> > >> with username/password things.  Hopefully others can chime in there.
> > >>
> > >> Thanks
> > >> Send
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> On Thu, Nov 4, 2021 at 2:06 PM Chris Sampson
> > >>  wrote:
> > >>>
> > >>> Worryingly, when I do get the Docker Image to build (further changes
> > to the
> > >>> Dockerfile), the auto-generated username and password from the
> startup
> > logs
> > >>> aren't being accepted for login via my