Re: [VOTE] Release Apache NiFi Flow Design System 0.3.0 RC2

2022-01-26 Thread Kevin Doran 
+1 binding

- Verified signature and hashes
- Checked License, Notice, Readme files
- Built using Node 16.13.2 (darmin-arm64)
- Ran demo app and it was working as expected

Thanks for this release, Scott!

-Kevin

> On Jan 26, 2022, at 09:26, David Handermann  
> wrote:
> 
> +1 binding
> 
> - Ran build using Node 16.13.2
> - Verified hashes and signatures
> - Verified License and Notice files
> 
> Thanks Scott!
> 
> Regards,
> David Handermann
> 
> On Wed, Jan 26, 2022 at 8:17 AM Shane Ardell 
> wrote:
> 
>> +1 (non-binding).
>> 
>> Performed all verification steps listed in the helper guide and ran the
>> demo app.
>> 
>> Thanks for RMing, Scott!
>> 
>> On Wed, Jan 26, 2022 at 9:12 AM Matt Gilman 
>> wrote:
>> 
>>> +1 (binding) Release this package as nifi-fds-0.3.0
>>> 
>>> Ran through release helper. Looks good. Thanks for RMing Scott!
>>> 
>>> Matt
>>> 
>>> On Tue, Jan 25, 2022 at 4:41 PM Scott Aslan 
>> wrote:
>>> 
 Hello,
 
 I am pleased to be calling this vote for the source release of Apache
>>> NiFi
 Flow Design System nifi-fds-0.3.0.
 
 The source zip, including signatures, etc. can be found at:
 https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0
 
 The Git tag is nifi-0.3.0-RC2
 The Git commit ID is a17b6712154f1b7bf36a04cfe728b61640843807
 
 
>>> 
>> https://gitbox.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=a17b6712154f1b7bf36a04cfe728b61640843807
 
 Checksums of nifi-fds-0.3.0-source-release.zip:
 SHA1: 92e473c2c0da9f031c47724ade9808f7572dd6bd
 SHA256:
>> 200c8f6a2a7fcdfa5a65c73dfef887c0173a9bf10d73ee7ac0160a614e9202ff
 SHA512:
 
 
>>> 
>> 74b93eb29a5e0bfefd25de288f387308307de63cf159f0c447565615a32b041fe5af20a326528a5dc8e99bf3adc8bbdc157cfa10090d51b30f958bb6253201b9
 
 Release artifacts are signed with the following key:
 https://people.apache.org/keys/committer/scottyaslan.asc
 
 KEYS file available here:
 https://dist.apache.org/repos/dist/release/nifi/KEYS
 
 17 issues were closed/resolved for this release:
 
 
>>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12345959
 
 Release note highlights can be found here:
 
 
>>> 
>> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.3.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-fds-0.3.0
 [ ] +0 no opinion
 [ ] -1 Do not release this package because...
 
>>> 
>>

Re: NiFi Parameter Context Question

2022-01-26 Thread Bryan Bende 
Hello,

1) I am not sure there is a definitive plan for removing variables
yet, but it is definitely something to consider for a NiFi 2.0 (or
other future release). I would also say that templates are in the same
situation.

Templates were created as a way for someone to share a part of a flow
with someone else, not really as a deployment mechanism. We have now
centered around the "flow definition" JSON used by NiFi Registry as
the format that should be used for importing/exporting/deploying. You
can right-click on a PG and Download Flow Definition, or create a new
PG and upload the flow definition JSON, or save/import to/from a NiFi
Registry. If you use this format, it does in fact capture the
parameter contexts and their initial values, minus sensitive values,
and it will create the contexts on import to a new NiFi instance.

2) This has come up a few times... it was an intentional decision to
not allow a sub-PG to inherit the param context from a parent PG, as
it becomes complicated to understand what value is actually going to
be resolved. However, I do think we need a user-friendly way to allow
setting the context on all sub-PGs. So if you were to configure a
top-level process group and set the param context, you would have an
option to select that all sub-PGs are also set to this. It is unclear
if/when this would be implemented, as someone would have to take on
the work to implement it.

Thanks,

Bryan

On Wed, Jan 26, 2022 at 11:05 AM Fredrick Pletz II
 wrote:
>
> Good morning,
> I love the introduction of parameters.  They satisfy a longstanding need for 
> managing multiple sensitive values from a single spot.  However, the 
> implementation does not satisfy the same functionality as variables.  Based 
> on the comment inside NiFi stating that parameters are replacing variables, 
> this has me worried that I'm going to lose significant functionality if 
> variables stop being supported.  Specifically, I use variables to assign 
> non-sensitive values throughout a NiFi in a way that can be transferred via 
> templates.  This allows me to create a generic template, deploy that 
> template, and configure the specifics by just setting a few variables.  It 
> has sped up deployment immensely.  Parameters don't transfer with templates, 
> and have to be added to every processing group.  I don't know of a way to 
> have all processing groups set to a parameter context all at once, so I would 
> end up needing to create the parameter context, add all the values, then add 
> that parameter context to dozens of processing groups.  This would be a major 
> step backward in streamlining deployments.
> Question 1) is NiFi planning to abandon support for variables?
> Question 2) is there a way to address the issues I have with parameter 
> contexts? - inability to assign a parameter context to ALL processing 
> groups, or even all sub-processing groups under a selected processing group   
>   - inability to transfer parameter context to new NiFi instances
> Fred Pletz

NiFi Parameter Context Question

2022-01-26 Thread Fredrick Pletz II 
Good morning,
I love the introduction of parameters.  They satisfy a longstanding need for 
managing multiple sensitive values from a single spot.  However, the 
implementation does not satisfy the same functionality as variables.  Based on 
the comment inside NiFi stating that parameters are replacing variables, this 
has me worried that I'm going to lose significant functionality if variables 
stop being supported.  Specifically, I use variables to assign non-sensitive 
values throughout a NiFi in a way that can be transferred via templates.  This 
allows me to create a generic template, deploy that template, and configure the 
specifics by just setting a few variables.  It has sped up deployment 
immensely.  Parameters don't transfer with templates, and have to be added to 
every processing group.  I don't know of a way to have all processing groups 
set to a parameter context all at once, so I would end up needing to create the 
parameter context, add all the values, then add that parameter context to 
dozens of processing groups.  This would be a major step backward in 
streamlining deployments.
Question 1) is NiFi planning to abandon support for variables?
Question 2) is there a way to address the issues I have with parameter 
contexts?     - inability to assign a parameter context to ALL processing 
groups, or even all sub-processing groups under a selected processing group     
- inability to transfer parameter context to new NiFi instances
Fred Pletz

Re: [VOTE] Release Apache NiFi Flow Design System 0.3.0 RC2

2022-01-26 Thread David Handermann 
+1 binding

- Ran build using Node 16.13.2
- Verified hashes and signatures
- Verified License and Notice files

Thanks Scott!

Regards,
David Handermann

On Wed, Jan 26, 2022 at 8:17 AM Shane Ardell 
wrote:

> +1 (non-binding).
>
> Performed all verification steps listed in the helper guide and ran the
> demo app.
>
> Thanks for RMing, Scott!
>
> On Wed, Jan 26, 2022 at 9:12 AM Matt Gilman 
> wrote:
>
> > +1 (binding) Release this package as nifi-fds-0.3.0
> >
> > Ran through release helper. Looks good. Thanks for RMing Scott!
> >
> > Matt
> >
> > On Tue, Jan 25, 2022 at 4:41 PM Scott Aslan 
> wrote:
> >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > Flow Design System nifi-fds-0.3.0.
> > >
> > > The source zip, including signatures, etc. can be found at:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0
> > >
> > > The Git tag is nifi-0.3.0-RC2
> > > The Git commit ID is a17b6712154f1b7bf36a04cfe728b61640843807
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=a17b6712154f1b7bf36a04cfe728b61640843807
> > >
> > > Checksums of nifi-fds-0.3.0-source-release.zip:
> > > SHA1: 92e473c2c0da9f031c47724ade9808f7572dd6bd
> > > SHA256:
> 200c8f6a2a7fcdfa5a65c73dfef887c0173a9bf10d73ee7ac0160a614e9202ff
> > > SHA512:
> > >
> > >
> >
> 74b93eb29a5e0bfefd25de288f387308307de63cf159f0c447565615a32b041fe5af20a326528a5dc8e99bf3adc8bbdc157cfa10090d51b30f958bb6253201b9
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/scottyaslan.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 17 issues were closed/resolved for this release:
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12345959
> > >
> > > Release note highlights can be found here:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.3.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-fds-0.3.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> >
>

Re: [VOTE] Release Apache NiFi Flow Design System 0.3.0 RC2

2022-01-26 Thread Shane Ardell 
+1 (non-binding).

Performed all verification steps listed in the helper guide and ran the
demo app.

Thanks for RMing, Scott!

On Wed, Jan 26, 2022 at 9:12 AM Matt Gilman  wrote:

> +1 (binding) Release this package as nifi-fds-0.3.0
>
> Ran through release helper. Looks good. Thanks for RMing Scott!
>
> Matt
>
> On Tue, Jan 25, 2022 at 4:41 PM Scott Aslan  wrote:
>
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > Flow Design System nifi-fds-0.3.0.
> >
> > The source zip, including signatures, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0
> >
> > The Git tag is nifi-0.3.0-RC2
> > The Git commit ID is a17b6712154f1b7bf36a04cfe728b61640843807
> >
> >
> https://gitbox.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=a17b6712154f1b7bf36a04cfe728b61640843807
> >
> > Checksums of nifi-fds-0.3.0-source-release.zip:
> > SHA1: 92e473c2c0da9f031c47724ade9808f7572dd6bd
> > SHA256: 200c8f6a2a7fcdfa5a65c73dfef887c0173a9bf10d73ee7ac0160a614e9202ff
> > SHA512:
> >
> >
> 74b93eb29a5e0bfefd25de288f387308307de63cf159f0c447565615a32b041fe5af20a326528a5dc8e99bf3adc8bbdc157cfa10090d51b30f958bb6253201b9
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/scottyaslan.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 17 issues were closed/resolved for this release:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12345959
> >
> > Release note highlights can be found here:
> >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.3.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-fds-0.3.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
>

Re: [VOTE] Release Apache NiFi Flow Design System 0.3.0 RC2

2022-01-26 Thread Matt Gilman 
+1 (binding) Release this package as nifi-fds-0.3.0

Ran through release helper. Looks good. Thanks for RMing Scott!

Matt

On Tue, Jan 25, 2022 at 4:41 PM Scott Aslan  wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> Flow Design System nifi-fds-0.3.0.
>
> The source zip, including signatures, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0
>
> The Git tag is nifi-0.3.0-RC2
> The Git commit ID is a17b6712154f1b7bf36a04cfe728b61640843807
>
> https://gitbox.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=a17b6712154f1b7bf36a04cfe728b61640843807
>
> Checksums of nifi-fds-0.3.0-source-release.zip:
> SHA1: 92e473c2c0da9f031c47724ade9808f7572dd6bd
> SHA256: 200c8f6a2a7fcdfa5a65c73dfef887c0173a9bf10d73ee7ac0160a614e9202ff
> SHA512:
>
> 74b93eb29a5e0bfefd25de288f387308307de63cf159f0c447565615a32b041fe5af20a326528a5dc8e99bf3adc8bbdc157cfa10090d51b30f958bb6253201b9
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/scottyaslan.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 17 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12345959
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.3.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-fds-0.3.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

Re: [VOTE] Release Apache NiFi Flow Design System 0.3.0 RC2

2022-01-26 Thread Adam Kocsis 
Verified all the steps.
+1 (non-binding)

On Wed, Jan 26, 2022 at 8:59 AM Andras Kovacs 
wrote:

> M Tien mtien.apa...@gmail.com via
>  nifi.apache.org
> 6:36 AM (2 hours ago)
> to dev
> English
> Hungarian
>
> Translate message
> Turn off for: English
> +1  (non-binding)
>
> - LICENSE and NOTICE look good
> - Verified that unit tests pass
> - Verified that build pass
> - Verified the demo app - everything looks as expected
>
> Thanks!
> András
>
>
> On Wed, Jan 26, 2022 at 6:36 AM M Tien  wrote:
>
> > +1
> >
> > - Verified checksums, signature,  and commit hash
> > - LICENSE and NOTICE look good
> > - Verified npm run clean:install passes
> > - Verified the demo app works as expected
> >
> > Thanks!
> >
> > - Margot
> >
> > > On Jan 25, 2022, at 2:39 PM, Joe Witt  wrote:
> > >
> > > +1 binding.
> > >
> > > Verified hashes, signature, L, commit.  Ran the build and demo app.
> > > Checks out fine.
> > >
> > > Please note we should not publish sha1 hashes anymore.  Just delete
> > > that from the artifacts.
> > >
> > > Thanks for RM efforts!
> > >
> > > Joe
> > >
> > > On Tue, Jan 25, 2022 at 2:41 PM Scott Aslan 
> > wrote:
> > >>
> > >> Hello,
> > >>
> > >> I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > >> Flow Design System nifi-fds-0.3.0.
> > >>
> > >> The source zip, including signatures, etc. can be found at:
> > >> https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0
> > >>
> > >> The Git tag is nifi-0.3.0-RC2
> > >> The Git commit ID is a17b6712154f1b7bf36a04cfe728b61640843807
> > >>
> >
> https://gitbox.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=a17b6712154f1b7bf36a04cfe728b61640843807
> > >>
> > >> Checksums of nifi-fds-0.3.0-source-release.zip:
> > >> SHA1: 92e473c2c0da9f031c47724ade9808f7572dd6bd
> > >> SHA256:
> 200c8f6a2a7fcdfa5a65c73dfef887c0173a9bf10d73ee7ac0160a614e9202ff
> > >> SHA512:
> > >>
> >
> 74b93eb29a5e0bfefd25de288f387308307de63cf159f0c447565615a32b041fe5af20a326528a5dc8e99bf3adc8bbdc157cfa10090d51b30f958bb6253201b9
> > >>
> > >> Release artifacts are signed with the following key:
> > >> https://people.apache.org/keys/committer/scottyaslan.asc
> > >>
> > >> KEYS file available here:
> > >> https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >>
> > >> 17 issues were closed/resolved for this release:
> > >>
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12345959
> > >>
> > >> Release note highlights can be found here:
> > >>
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.3.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-fds-0.3.0
> > >> [ ] +0 no opinion
> > >> [ ] -1 Do not release this package because...
> >
> >
>

Re: [VOTE] Release Apache NiFi Flow Design System 0.3.0 RC2

2022-01-26 Thread Andras Kovacs 
M Tien mtien.apa...@gmail.com via
 nifi.apache.org
6:36 AM (2 hours ago)
to dev
English
Hungarian

Translate message
Turn off for: English
+1  (non-binding)

- LICENSE and NOTICE look good
- Verified that unit tests pass
- Verified that build pass
- Verified the demo app - everything looks as expected

Thanks!
András


On Wed, Jan 26, 2022 at 6:36 AM M Tien  wrote:

> +1
>
> - Verified checksums, signature,  and commit hash
> - LICENSE and NOTICE look good
> - Verified npm run clean:install passes
> - Verified the demo app works as expected
>
> Thanks!
>
> - Margot
>
> > On Jan 25, 2022, at 2:39 PM, Joe Witt  wrote:
> >
> > +1 binding.
> >
> > Verified hashes, signature, L, commit.  Ran the build and demo app.
> > Checks out fine.
> >
> > Please note we should not publish sha1 hashes anymore.  Just delete
> > that from the artifacts.
> >
> > Thanks for RM efforts!
> >
> > Joe
> >
> > On Tue, Jan 25, 2022 at 2:41 PM Scott Aslan 
> wrote:
> >>
> >> Hello,
> >>
> >> I am pleased to be calling this vote for the source release of Apache
> NiFi
> >> Flow Design System nifi-fds-0.3.0.
> >>
> >> The source zip, including signatures, etc. can be found at:
> >> https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0
> >>
> >> The Git tag is nifi-0.3.0-RC2
> >> The Git commit ID is a17b6712154f1b7bf36a04cfe728b61640843807
> >>
> https://gitbox.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=a17b6712154f1b7bf36a04cfe728b61640843807
> >>
> >> Checksums of nifi-fds-0.3.0-source-release.zip:
> >> SHA1: 92e473c2c0da9f031c47724ade9808f7572dd6bd
> >> SHA256: 200c8f6a2a7fcdfa5a65c73dfef887c0173a9bf10d73ee7ac0160a614e9202ff
> >> SHA512:
> >>
> 74b93eb29a5e0bfefd25de288f387308307de63cf159f0c447565615a32b041fe5af20a326528a5dc8e99bf3adc8bbdc157cfa10090d51b30f958bb6253201b9
> >>
> >> Release artifacts are signed with the following key:
> >> https://people.apache.org/keys/committer/scottyaslan.asc
> >>
> >> KEYS file available here:
> >> https://dist.apache.org/repos/dist/release/nifi/KEYS
> >>
> >> 17 issues were closed/resolved for this release:
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12345959
> >>
> >> Release note highlights can be found here:
> >>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.3.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-fds-0.3.0
> >> [ ] +0 no opinion
> >> [ ] -1 Do not release this package because...
>
>